about summary refs log tree commit diff stats
path: root/shell/data.limg
Commit message (Collapse)AuthorAgeFilesLines
* shell: moar macrosKartik K. Agaram2021-06-051-41/+42
|
* .Kartik K. Agaram2021-06-041-2/+0
|
* .Kartik K. Agaram2021-06-041-5/+5
|
* .Kartik K. Agaram2021-06-041-2/+2
|
* .Kartik K. Agaram2021-06-041-1/+1
|
* more convenient 'def'Kartik K. Agaram2021-06-041-30/+32
|
* rename the definition primitive to 'def'Kartik K. Agaram2021-06-041-17/+17
|
* .Kartik Agaram2021-05-311-17/+19
| | | | State as of https://archive.org/details/akkartik-mu-2021-05-31
* .Kartik K. Agaram2021-05-311-3/+3
|
* data.limg now loading properly againKartik K. Agaram2021-05-311-1/+1
|
* .Kartik K. Agaram2021-05-221-1/+1
|
* .Kartik K. Agaram2021-05-191-2/+2
|
* shell: roll back a change to the 'when' macroKartik K. Agaram2021-05-151-2/+2
| | | | | Introduced in commit 1adc904ef3 from a week ago, but it turns out brcircle has been consistently broken ever since.
* A 'bowboard', a chessboard of rainbow circlesKartik K. Agaram2021-05-081-23/+31
| | | | Compare with (chessboard screen 256)
* a full-circle rainbowKartik K. Agaram2021-05-081-2/+29
|
* new shell macro: doKartik K. Agaram2021-05-071-2/+3
|
* .Kartik K. Agaram2021-05-071-3/+5
|
* .Kartik K. Agaram2021-05-071-19/+19
|
* clean up all definitionsKartik K. Agaram2021-05-071-21/+20
|
* clean up chessboardKartik K. Agaram2021-05-071-10/+12
| | | | | We still benefit from some helpers here because of the unrolling and multiple calls to helpers.
* clean up read_lineKartik K. Agaram2021-05-071-9/+6
|
* clean up Bresenham line-drawingKartik K. Agaram2021-05-071-26/+22
|
* no, we need hline1 for fill_rectKartik K. Agaram2021-05-071-8/+10
|
* clean up hline and vlineKartik K. Agaram2021-05-071-10/+10
|
* starting to implement first macrosKartik K. Agaram2021-05-071-0/+4
| | | | | | | | | | | | | | | Another commit, another bugfix. Some snippets from my currently exploding todo list: - always investigate lookup errors immediately. Beyond the root cause, they should never happen at the moment, while we aren't reclaiming memory. we should always return a more precise error message. Usually involving null pointer checks. - on abort, print out stack trace - emit mapping of labels to addresses during survey - store a mapping of symbols somewhere in the code image - stop allocating 1KB per token; expand space for tokens as needed
* belatedly migrate stale example definitionsKartik K. Agaram2021-05-061-91/+91
| | | | | Also bare-bones syntax highlighting for .limg files. Doesn't work when .limg file is first file opened with Vim.
* bresenham circlesKartik K. Agaram2021-04-251-1/+22
| | | | Known issue: circles of radius 9 crash. (Multiples of 9 overflow the trace.)
* bug in bresenham linesKartik K. Agaram2021-04-251-2/+2
|
* shell: primitives 'and' and 'or'Kartik K. Agaram2021-04-251-11/+1
|
* .Kartik K. Agaram2021-04-251-0/+84