about summary refs log tree commit diff stats
path: root/apps/tile
Commit message (Collapse)AuthorAgeFilesLines
* 7036Kartik Agaram2020-10-151-6/+1
| | | | ctrl-u now working.
* 7035Kartik Agaram2020-10-152-4/+6
| | | | | ctrl-f and ctrl-b working right. Now ctrl-u is segfaulting. Also expanding words.
* 7034Kartik Agaram2020-10-152-3/+8
| | | | | Finally following up on commit 7020. Ctrl-a and ctrl-e now work, but word-wise motions are still showing some funkiness.
* 7021Kartik Agaram2020-10-142-2/+6
|
* 7020Kartik Agaram2020-10-143-182/+89
| | | | | | | | | snapshot: migrating call-path to store word handles rather than word indexes. ctrl-a and ctrl-e are segfaulting. There are likely other problems. The major new change here is that allocating a call-path-element no longer initializes it.
* 7019Kartik Agaram2020-10-141-3/+3
|
* 7018 - tile: tweak spacing between stacksKartik Agaram2020-10-132-17/+19
| | | | | Until now the word being typed had a slightly larger invisible margin, which was a little strange. Should look cleaner now.
* 7017Kartik Agaram2020-10-131-14/+14
|
* 7015 - bugfix in column width computationKartik Agaram2020-10-132-9/+15
| | | | | I just got bitten by variable shadowing! It's a lot less theoretical concern now.
* 7014Kartik Agaram2020-10-122-5/+28
| | | | 7013 had broken right-justification when rendering the stack. Redo.
* 7013Kartik Agaram2020-10-123-50/+1
|
* 7011 - tile: keep garbage out of the stackKartik Agaram2020-10-122-13/+14
|
* 7010Kartik Agaram2020-10-122-1/+44
| | | | A new example that better demonstrates the value of named arguments.
* 7009 - tile: real hotkey to quitKartik Agaram2020-10-122-1/+6
|
* 7008 - tile: center menuKartik Agaram2020-10-111-0/+3
|
* 7007 - tile: hotkey to clear sandboxKartik Agaram2020-10-111-0/+16
| | | | | | Alternative symbols considered for the menu option: ∅ AC (like in a calculator)
* 7006Kartik Agaram2020-10-111-2/+10
|
* 7005 - tile: move to start/end of lineKartik Agaram2020-10-112-13/+39
|
* 7004Kartik Agaram2020-10-111-4/+5
|
* 7003Kartik Agaram2020-10-111-4/+4
|
* 7002 - tile: next-wordKartik Agaram2020-10-112-1/+39
|
* 7001Kartik Agaram2020-10-111-8/+3
|
* 7000 - tile: previous-word also bumps up to callerKartik Agaram2020-10-113-53/+34
|
* 6999 - tile: move to previous wordKartik Agaram2020-10-101-0/+15
|
* 6998Kartik Agaram2020-10-101-1/+1
|
* 6997Kartik Agaram2020-10-101-0/+10
|
* 6996Kartik Agaram2020-10-101-14/+1
|
* 6995Kartik Agaram2020-10-101-6/+3
|
* 6994Kartik Agaram2020-10-101-1/+1
|
* 6993Kartik Agaram2020-10-101-9/+4
|
* 6992Kartik Agaram2020-10-101-1/+1
| | | | | | Left arrow key out of an expanded word now working. Still to fix: left arrow key out of the first word in the first word.
* 6991 - tile: nested calls now expandingKartik Agaram2020-10-103-242/+64
| | | | | | | I just needed to remove an obsolete guardrail in render-line. Still seeing some bugs with left-arrow when playing around with the full expansion of `1 2+`.
* 6990Kartik Agaram2020-10-101-54/+82
| | | | | Bring back definitions for 1+ and 2+. Expanding nested calls still doesn't work.
* 6989 - tile: arrow keys now seem to handle callsKartik Agaram2020-10-101-6/+15
|
* 6988Kartik Agaram2020-10-101-30/+242
| | | | | Oh, of course. I can't compare the word with the word at the cursor. Not even its interned pointer. We have to track the call path.
* 6987 - left-arrow to jump to caller/calleeKartik Agaram2020-10-103-91/+234
| | | | | | | Starting to work. I'm still seeing problems in lines with multiple expanded calls, but perhaps that's a rendering issue. The code is absolutely ghastly.
* 6986Kartik Agaram2020-10-091-1/+23
| | | | Cursor now stays on the right row as we bounce in and out of function calls.
* 6985 - tile: make calls read-onlyKartik Agaram2020-10-091-0/+8
|
* 6984Kartik Agaram2020-10-091-8/+13
|
* 6983 - tile: right-arrow can now move out of callsKartik Agaram2020-10-091-0/+15
|
* 6982 - right-arrow now moves into expanded callsKartik Agaram2020-10-092-8/+124
| | | | | | | | | | | | Rendering is still ugly. Cursor isn't on the right row. But the hard part is behind us. This was a stupid mistake in function-body, and it happened because I've been getting lazy and passing (addr handle) objects when I should be passing in "constant" addr objects. I'm not sure why I was so resistant to debugging by print here. I spent 3 days waffling about with this bug.
* 6981Kartik Agaram2020-10-091-16/+14
| | | | Tile: simplify the contract for render-column.
* 6980Kartik Agaram2020-10-091-3/+2
| | | | Changing tack..
* 6979Kartik Agaram2020-10-092-3/+3
| | | | | Use the fake-screen infrastructure we already have for non-interactive mode.
* 6978Kartik Agaram2020-10-091-0/+36
| | | | | | We don't have tests yet in the tile prototype, mostly because we don't yet feel confident about what desired behavior should be. But it's still helpful to have a non-interactive mode for tracking down segfaults.
* 6977Kartik Agaram2020-10-092-14/+50
| | | | | Snapshot. We've gotten arrow keys navigating, but segfault when getting to the second word in an expanded function call body.
* 6976Kartik Agaram2020-10-091-4/+4
|
* 6975Kartik Agaram2020-10-091-1/+1
|
* 6974Kartik Agaram2020-10-081-10/+10
|
* 6972 - tile: stop persisting cursor-wordKartik Agaram2020-10-082-26/+94
| | | | Rather surprisingly, this transformation worked the first time!