about summary refs log tree commit diff stats
Commit message (Collapse)AuthorAgeFilesLines
...
* .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
|
* .Kartik K. Agaram2021-11-091-28/+0
|
* .Kartik K. Agaram2021-11-081-18/+12
|
* state priorities in ReadmeKartik K. Agaram2021-11-081-2/+5
|
* .Kartik K. Agaram2021-11-071-2/+2
|
* more tweaks to ReadmeKartik K. Agaram2021-11-071-22/+25
|
* .Kartik K. Agaram2021-11-071-1/+2
|
* .Kartik K. Agaram2021-11-071-0/+0
|
* .Kartik K. Agaram2021-11-071-0/+1
|
* update screenshotKartik K. Agaram2021-11-072-0/+0
|
* switch menu bars to reverse videoKartik K. Agaram2021-11-072-9/+9
|
* update screenshotKartik K. Agaram2021-11-071-0/+0
|
* delete some Lua 5.1 thingsKartik K. Agaram2021-11-0737-1765/+0
| | | | These are likely to suffer bitrot.
* fix menu colorsKartik K. Agaram2021-11-071-3/+2
| | | | I had it switching to a dark background on me.
* better support light backgroundsKartik K. Agaram2021-11-071-0/+1
| | | | Thanks nicolas decoster for reporting this issue.
* more obvious phrasingKartik K. Agaram2021-11-071-7/+4
| | | | Early returns are only worthwhile if they're utterly obvious.
* fix a regression in commit ee85ad384f17Kartik K. Agaram2021-11-071-0/+1
|
* .Kartik K. Agaram2021-11-071-1/+1
|
* apps don't need to setlocale; it's hardcodedKartik K. Agaram2021-11-061-1/+0
|
* .Kartik K. Agaram2021-11-061-4/+2
|
* syntax highlighting on GitHubKartik K. Agaram2021-11-061-0/+1
|
* game of lifeKartik K. Agaram2021-11-063-1/+204
| | | | | This required me to figure out some unicode-related nuances, but no new primitives.
* .Kartik K. Agaram2021-11-061-3/+1
|
* window:nodelay() for non-blocking inputKartik K. Agaram2021-11-061-0/+16
|
* .Kartik K. Agaram2021-11-061-0/+12
|
* .Kartik K. Agaram2021-11-061-10/+16
|
* .Kartik K. Agaram2021-11-061-1/+2
|
* escape hatch to quit with a pending errorKartik K. Agaram2021-11-062-5/+14
|
* .Kartik K. Agaram2021-11-061-0/+0
|
* .Kartik K. Agaram2021-11-061-2/+2
|
* reorg editor transitionsKartik K. Agaram2021-11-062-12/+13
|
* start showing error messages in editorKartik K. Agaram2021-11-063-7/+21
| | | | | | | | | | | Before we'd end up in cryptic situations where error messages would get hidden when the program got out of ncurses mode. Now it's a little nicer with error messages showing up at the bottom of the editor. But there's still a problem: there's no way to abort without fixing an error.
generated by cgit-pink 1.4.1-2-gfad0 (git 2.36.2.497.gbbea4dcf42) at 2024-11-16 03:51:14 +0000