about summary refs log tree commit diff stats
path: root/shell
Commit message (Collapse)AuthorAgeFilesLines
* almost there; this is encouragingKartik K. Agaram2021-06-221-16/+21
| | | | The at-head-of-list? is a really ugly hack, though.
* beginnings of tokenization within symbolsKartik K. Agaram2021-06-222-17/+68
| | | | We're now down to 4 failing tests. But these will require surgery.
* .Kartik K. Agaram2021-06-221-11/+3
|
* clean up lexical categoriesKartik K. Agaram2021-06-222-142/+48
|
* snapshotKartik K. Agaram2021-06-221-3/+32
| | | | | Still a couple of failing tests before I switch gears to breaking down symbols containing infix.
* .Kartik K. Agaram2021-06-221-3/+5
|
* snapshot: infixKartik K. Agaram2021-06-225-9/+542
| | | | | | | | | | | | | | | | | | | | | Like parenthesize, I'm copying tests over from https://github.com/akkartik/wart Unlike parenthesize, though, I can't just transliterate the code itself. Wart was operating on an intermediate AST representation. Here I'm all the way down to cells. That seemed like a good idea when I embarked, but now I'm not so sure. Operating with the right AST data structure allowed me to more easily iterate over the elements of a list. The natural recursion for cells is not a good fit. This patch and the next couple is an interesting case study in what makes Unix so effective. Yes, you have to play computer, and yes it gets verbose and ugly. But just diff and patch go surprisingly far in helping build a picture of the state space in my brain. Then again, there's a steep gradient of skills here. There are people who can visualize state spaces using diff and patch far better than me, and people who can't do it as well as me. Nature, nurture, having different priorities, whatever the reason. Giving some people just the right crutch excludes others.
* .Kartik K. Agaram2021-06-213-67/+89
|
* start implementing infixKartik K. Agaram2021-06-211-281/+3
| | | | First step: undo operator support in tokenization.
* .Kartik K. Agaram2021-06-201-3/+3
|
* shell: now no definitions with long linesKartik K. Agaram2021-06-201-3/+7
|
* shell: shrink definition widths in a few placesKartik K. Agaram2021-06-201-12/+14
| | | | The only remaining long lines now are in 'pair' and 'with'.
* this is how we create aliasesKartik K. Agaram2021-06-201-1/+1
|
* preserve indentation of the sandboxKartik K. Agaram2021-06-203-7/+7
|
* 'with' lets us drop a few more parensKartik K. Agaram2021-06-201-40/+41
|
* new macro: withKartik K. Agaram2021-06-204-4/+66
|
* new macro: retKartik K. Agaram2021-06-201-6/+7
| | | | http://arclanguage.org/item?id=11068
* start dropping parens everywhereKartik K. Agaram2021-06-201-96/+98
|
* start guessing parentheses based on indentationKartik K. Agaram2021-06-202-61/+50
|
* snapshotKartik K. Agaram2021-06-204-3/+552
| | | | | This is going better than expected; just 3 failing tests among the new ones.
* start emitting indent tokensKartik K. Agaram2021-06-184-29/+224
|
* redo next-token in more high-level termsKartik K. Agaram2021-06-181-73/+93
|
* .Kartik K. Agaram2021-06-181-30/+30
|
* .Kartik K. Agaram2021-06-181-49/+49
|
* start emitting token for newlineKartik K. Agaram2021-06-181-5/+12
|
* newlines are now a tokenKartik K. Agaram2021-06-182-4/+12
|
* start implementing indent-sensitivityKartik K. Agaram2021-06-181-2/+26
| | | | | | | General plan: stop skipping newlines during tokenization introduce a new indent token, initially skip it transparently start doing cleverer things
* .Kartik K. Agaram2021-06-181-6/+2
|
* .Kartik K. Agaram2021-06-181-8/+6
|
* make code in Readme easier to copyKartik K. Agaram2021-06-181-6/+6
| | | | Thanks Sumeet Agarwal for the suggestion.
* shell: stop punning tokens as cellsKartik K. Agaram2021-06-183-89/+116
|
* change precision when loading sandbox codeSumeet Agarwal2021-06-171-2/+2
|
* shell: better screenshotKartik Agaram2021-06-151-1/+1
|
* always print black pixels when rendering screensKartik K. Agaram2021-06-151-2/+0
| | | | This is an old 'optimization' that turns out to not actually matter.
* shell: improve docsKartik Agaram2021-06-151-5/+14
|
* .Kartik Agaram2021-06-151-33/+34
|
* document responsiveness trade-offKartik K. Agaram2021-06-152-35/+28
|
* do more work per fake-screen refreshKartik K. Agaram2021-06-151-1/+1
| | | | | | Refreshing the fake screen is still a heavyweight operation. Double-buffering makes it less obvious but doesn't actually reduce the amount of work. We need to ensure that we do enough work between refreshes to make them economic.
* more precisely track count of calls to evalKartik K. Agaram2021-06-152-20/+13
| | | | | Before I only separately counted calls at each stack depth. I don't remember if that seemed good enough or was just an oversight.
* flickerlessly render fake screens in environmentKartik K. Agaram2021-06-152-34/+10
| | | | | | | | Font rendering now happens off the real screen, which provides the effect of double-buffering. Apps can now also use convert-graphemes-to-pixels for more traditional double-buffering.
* periodic run of misc_checksKartik K. Agaram2021-06-121-2/+2
| | | | | I should really stop using /disp8 jumps at the top-level given how inconvenient it is to check for overly large offsets.
* .Kartik K. Agaram2021-06-127-178/+138
| | | | | Roll back to commit 70919b45f0. Recent commits add lots of extra function args for dubious benefit.
* snapshotKartik K. Agaram2021-06-121-12/+41
| | | | Looks like what's slowing down screen rendering is in fact _font_ rendering.
* .Kartik K. Agaram2021-06-121-16/+14
|
* trying to eliminate flicker when rendering screenKartik K. Agaram2021-06-121-13/+26
| | | | | | | | | | | | | | | | | | | Two interesting things: - We don't really need double-buffering for rendering the screen on the sandbox as a progress indicator. Everything else is untouched, and render-screen should be doing that as well. - Rendering just pixels of the fake screen is buttery smooth. It's the _graphemes_ that are slowing things down. Even though there's so many fewer of them! As a result, drawing the fake screen less frequently in `evaluate` doesn't actually help with flicker. Even though it'll make the debug cycle shorter. So my current plan is to attack flicker in isolation before I mess with the render frequency. In this commit I optimized away the cursor handling. Still doesn't seem to be helping. In fact it actually seems _worse_.
* eliminate some implicit writes to real screenKartik K. Agaram2021-06-127-120/+120
|
* .Kartik K. Agaram2021-06-125-66/+69
| | | | | | Rename cells containing screens to screen vars because of the ambiguity that each grapheme in fake screens is represented by a type screen-cell. While we're at it, we also analogously rename keyboard vars.
* shell: larger fake screenKartik K. Agaram2021-06-124-37/+41
|
* .Kartik Agaram2021-06-111-3/+3
|
* .Kartik K. Agaram2021-06-111-42/+1
|
generated by cgit-pink 1.4.1-2-gfad0 (git 2.36.2.497.gbbea4dcf42) at 2024-07-03 08:55:29 +0000