about summary refs log tree commit diff stats
path: root/src
Commit message (Collapse)AuthorAgeFilesLines
...
* drop some redundant `require`sKartik K. Agaram2021-11-201-14/+7
|
* luasocket now loading properlyKartik K. Agaram2021-11-206-6/+12
| | | | I still haven't tried actually running it.
* renameKartik K. Agaram2021-11-202-1/+1
|
* extract a helperKartik K. Agaram2021-11-201-8/+17
|
* inline luasocketKartik K. Agaram2021-11-2051-1/+9430
| | | | Just builds for now, isn't available yet to Lua code.
* bugfix: support running from top-levelKartik K. Agaram2021-11-201-1/+1
| | | | Unfortunately we can't currently run teliva from anywhere else :/
* get rid of a distracting nameKartik K. Agaram2021-11-203-4/+4
| | | | | No distinction now between the C and Lua versions of the curses library. We build them all together in one place.
* port changes from minimal to maximal versionKartik K. Agaram2021-11-205-531/+47
| | | | From lcurseslib.c to lcurses/ directory.
* report errors when calling non-existent functionsKartik K. Agaram2021-11-201-2/+4
|
* inline in C is not worth the troubleKartik K. Agaram2021-11-201-2/+2
| | | | https://merveilles.town/@akkartik/107310347838372198
* inline lcurses maximally rather than minimallyKartik K. Agaram2021-11-1912-4/+4991
| | | | | | | | | Until now we had just the bare minimum bindings needed for the demos built so far. Now we have all of lcurses building in place with minimal changes. The changes in this commit can run hanoi.lua when inlined into Lua 5.1, but don't work with Teliva.
* tested on Mac OSKartik K. Agaram2021-11-141-1/+1
|
* import life.teliva into image formatKartik K. Agaram2021-11-141-0/+1
|
* cleaner error handlingKartik K. Agaram2021-11-142-21/+9
|
* .Kartik K. Agaram2021-11-141-2/+1
|
* remain in editor on errorKartik K. Agaram2021-11-142-5/+31
|
* .Kartik K. Agaram2021-11-142-3/+3
|
* find _some_ way to show error on initial loadKartik K. Agaram2021-11-141-2/+8
|
* more menu cleanupKartik K. Agaram2021-11-142-8/+16
|
* .Kartik K. Agaram2021-11-142-20/+20
|
* drop support for non-image Lua scriptsKartik K. Agaram2021-11-141-35/+8
| | | | We still have no story for error messages. We'll work on that next.
* draw the browse dialog the same wayKartik K. Agaram2021-11-142-10/+46
|
* dialogs are not status messagesKartik K. Agaram2021-11-141-3/+8
|
* smarter image browsingKartik K. Agaram2021-11-141-19/+53
| | | | | - distinguish between unused functions and data - don't hardcode a specific convention for the curses window object
* slightly more robust on-disk formatKartik K. Agaram2021-11-141-2/+2
| | | | | | Looks like Lua supports a little bit of programmability in its multi-line string literals. Even though I can't find this documented anywhere.
* janky way to cancel browsingKartik K. Agaram2021-11-141-6/+9
|
* slightly more obvious browse dialogKartik K. Agaram2021-11-141-1/+4
|
* cleaner dialogsKartik K. Agaram2021-11-142-23/+60
|
* no, use Esc to cancelKartik K. Agaram2021-11-141-5/+5
| | | | | It inserts an ugly pause for ghastly historical reasons having to do with the origins of terminals. But hopefully this isn't a common case.
* use word at cursor when it's not at start of lineKartik K. Agaram2021-11-141-2/+4
|
* editor: use ctrl-g to cancel dialogsKartik K. Agaram2021-11-131-5/+5
|
* jump to word at cursor by defaultKartik K. Agaram2021-11-131-0/+28
|
* ctrl-u to clear response in go menuKartik K. Agaram2021-11-131-0/+3
|
* reset cursor position when switching definitionsKartik K. Agaram2021-11-131-0/+2
|
* .Kartik K. Agaram2021-11-131-1/+0
|
* cleaner layout for a function's code and dataKartik K. Agaram2021-11-132-9/+54
|
* .Kartik K. Agaram2021-11-131-0/+1
|
* .Kartik K. Agaram2021-11-131-4/+1
|
* .Kartik K. Agaram2021-11-131-1/+1
|
* generalize kilo's hard-coded multiline C syntaxKartik K. Agaram2021-11-131-21/+28
|
* .Kartik K. Agaram2021-11-131-6/+2
|
* fix for editor highlightingKartik K. Agaram2021-11-131-1/+2
| | | | Bug introduced during the transition to ncurses.
* clean up after the editorKartik K. Agaram2021-11-131-0/+1
| | | | | Even though we don't need to leave ncurses mode, there's still a process boundary to clean up before.
* .Kartik K. Agaram2021-11-132-3/+4
|
* .Kartik K. Agaram2021-11-132-8/+7
|
* kill highlighting flagsKartik K. Agaram2021-11-131-9/+5
| | | | Looks like they were never used in original Kilo.
* replace Kilo's raw terminal handling with ncursesKartik K. Agaram2021-11-133-357/+92
| | | | | | This was on my todo list. What made it urgent was finding that calling getch() even once while in ncurses caused Kilo to stop detecting arrow keys. No need to debug that sort of nonsense.
* avoid side-effects on the Lua stackKartik K. Agaram2021-11-131-0/+5
|
* stop leaking memoryKartik K. Agaram2021-11-132-4/+6
|
* memory corruption bugKartik K. Agaram2021-11-131-1/+3
| | | | | | | | | I was saving an address on the stack to a global, and it was getting clobbered later. This is the sort of thing I completely eliminated in https://github.com/akkartik/mu :/ Now I'm taking a leaf out of the Mu playbook and leaking a little bit of memory every time I switch definitions.
generated by cgit-pink 1.4.1-2-gfad0 (git 2.36.2.497.gbbea4dcf42) at 2024-11-15 12:24:19 +0000