about summary refs log tree commit diff stats
Commit message (Collapse)AuthorAgeFilesLines
...
* 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.
* .Kartik K. Agaram2021-11-131-6/+0
|
* very rudimentary definition browserKartik K. Agaram2021-11-131-3/+25
| | | | Never shows definitions that were never called. Including non-functions.
* .Kartik K. Agaram2021-11-131-3/+3
|
* .Kartik K. Agaram2021-11-131-9/+0
|
* .Kartik K. Agaram2021-11-131-5/+9
|
* shield kilo.c from teliva_editbuffer detailKartik K. Agaram2021-11-132-4/+10
|
* .Kartik K. Agaram2021-11-131-2/+5
|
* .Kartik K. Agaram2021-11-131-1/+1
|
* .Kartik K. Agaram2021-11-132-10/+8
|
* .Kartik K. Agaram2021-11-131-3/+3
|
* .Kartik K. Agaram2021-11-132-22/+20
|
* clean up experiment from previous commitKartik K. Agaram2021-11-131-10/+0
|
* instrumenting function calls with their depthKartik K. Agaram2021-11-134-2/+66
|
* start using static linkage like the rest of LuaKartik K. Agaram2021-11-132-48/+44
|
* learning about Lua's debug infrastructureKartik K. Agaram2021-11-111-0/+21
| | | | https://www.lua.org/pil/23.2.html
* create empty file when navigating to empty definitionKartik K. Agaram2021-11-112-4/+4
|
* fix incorrect hotkey in menuKartik K. Agaram2021-11-111-2/+2
|
* ctrl-g to edit a different definitionKartik K. Agaram2021-11-112-3/+68
|
* gracefully handle missing definitionKartik K. Agaram2021-11-111-0/+1
|
* .Kartik K. Agaram2021-11-111-5/+5
|
* global for current definition being editedKartik K. Agaram2021-11-111-3/+5
|
* pass lua_State into editorKartik K. Agaram2021-11-112-6/+6
|
* delete a helper that hides stack side effectsKartik K. Agaram2021-11-111-8/+2
|
* extract a few helper functionsKartik K. Agaram2021-11-111-21/+26
|
* .Kartik K. Agaram2021-11-111-14/+14
|
* .Kartik K. Agaram2021-11-111-1/+1
|
* reorgKartik K. Agaram2021-11-112-48/+44
|
* .Kartik K. Agaram2021-11-111-0/+1
|
* edit a single hard-coded definition in the imageKartik K. Agaram2021-11-103-8/+71
| | | | | | | | | | | | | src/teliva counter.tlv C-e # switch to editor C-e # save and quit C-x # exit counter.tlv now has the same logical contents, though the whitespace has changed, and the order of keys is different. The implementation is utterly ghastly. For one, I'm unnecessarily interfacing with kilo through the file system.
* .Kartik K. Agaram2021-11-101-25/+25
|
* .Kartik K. Agaram2021-11-101-23/+23
|
* new .tlv image formatKartik K. Agaram2021-11-102-0/+109
| | | | | | | | | | | | | | Plan is for this to be the default representation for Teliva programs. Text-friendly but not meant to be edited directly as text. Will eventually include both code and data definitions, both current snapshot and past revision history. Right now .tlv files seem to run. Error checking is non-existent, because I don't understand Lua's idioms around 'status' yet. Opening the editor expectedly segfaults. This commit is the most mind-bending bit of code I've written in a long time.
* main function for other apps besides life.telivaKartik K. Agaram2021-11-104-51/+56
|
* extract side-effect from 'update'Kartik K. Agaram2021-11-101-3/+4
|
* .Kartik K. Agaram2021-11-101-7/+10
| | | | | | | | | | one more implication: - the menu table. It feels natural to define it alongside keyboard input. However, it may then not be initialized during the first paint of the app. I'm not sure how I feel about the menu data structure being defined far away from the `update` function. Recipe for it to go out of date.
* no, initialize globals in symmetry with functionsKartik K. Agaram2021-11-101-15/+18
| | | | | | | | | | | | | | | | Current plan: definitions can have arbitrary code. They'll be loaded lazily when a specific name is invoked but has no binding. Implications: - It'll be the responsibility of the code to define the name it's saved in. "Phony" names will result in some fragments of code repeatedly executing. - Assigning a global to nil is a way to retrigger its initialization the next time it's needed. I'm not sure how I feel about this sort of incompatibility with Lua. I suppose we could avoid it by also tracking what definitions have already been loaded in a run.
* put all code into some functionKartik K. Agaram2021-11-101-136/+94
|
* remove upstream ReadmesKartik K. Agaram2021-11-101-61/+2
| | | | They're already growing bitrot.
* life: fix loaf patternKartik K. Agaram2021-11-101-2/+5
|
* life: bugfix in up arrowKartik K. Agaram2021-11-101-1/+1
|
* life: move starting pattern around on the screenKartik K. Agaram2021-11-103-1/+128
| | | | | | This assumes we're doing it early soon after opening a new pattern, when it hasn't yet reached the margins. Quick and dirty, but seems good enough.
* .Kartik K. Agaram2021-11-101-1/+6
|
* why do we refresh screen after reading keyboard?Kartik K. Agaram2021-11-102-4/+0
|
* load standard Game of Life pattern filesKartik K. Agaram2021-11-101-0/+47
|
* some commandline options for life.telivaKartik K. Agaram2021-11-101-5/+43
|
* drop an obsolete build targetKartik K. Agaram2021-11-101-3/+0
|
generated by cgit-pink 1.4.1-2-gfad0 (git 2.36.2.497.gbbea4dcf42) at 2025-07-18 19:57:42 +0000