about summary refs log tree commit diff stats
Commit message (Collapse)AuthorAgeFilesLines
* .Kartik K. Agaram2021-11-261-2/+2
|
* .Kartik K. Agaram2021-11-261-2/+2
|
* extract a functionKartik K. Agaram2021-11-251-10/+18
|
* more stack hygieneKartik K. Agaram2021-11-251-0/+2
|
* one more curses bindingKartik K. Agaram2021-11-251-0/+1
|
* libraries don't need Lua's `#define`s and whatnotKartik K. Agaram2021-11-251-2/+2
|
* .Kartik K. Agaram2021-11-251-1/+1
|
* .Kartik K. Agaram2021-11-251-7/+7
|
* dedup definitions in big-picture viewKartik K. Agaram2021-11-251-4/+40
| | | | We only want to show most recent version of each binding.
* new shortcut: return to big-picture viewKartik K. Agaram2021-11-252-12/+32
|
* teliva is now ASan-clean againKartik K. Agaram2021-11-252-2/+6
| | | | | | | | | At least in short runs. Encouraging that the problem was in a recent commit (5a63a5ca40 from yesterday when I introduced version control). Disabling Address Sanitizer again.
* make upstream kilo ASan-cleanKartik K. Agaram2021-11-251-3/+4
| | | | | | Many thanks to dirkf for https://github.com/antirez/kilo/pull/73! However, teliva is still not ASan-clean.
* temporarily start using the address sanitizerKartik K. Agaram2021-11-251-2/+2
|
* jettison luacKartik K. Agaram2021-11-253-439/+2
| | | | | | | | | I'm starting to see some heap buffer overruns, which means we have too much C code. I noticed this because editing life.tlv no longer works after commit 5a63a5ca4. However, the offending heap overrun has been around long before that. It's just been a silent bug until now.
* renameKartik K. Agaram2021-11-241-9/+9
|
* monotonically accumulate versions of definitionsKartik K. Agaram2021-11-245-85/+259
| | | | | | | | | | | One old drawback now has a new look. Before, we loaded definitions in order, so global definitions had to exist before other global definitions that used them. See window and grid in life.tlv. Now we load definitions in reverse order, so initialization needs to change. Worse, if we update window, we need to edit grid just to fix the order. This implies that we can't yet optimize away bindings where there are no new changes.
* more Makefile streamliningKartik K. Agaram2021-11-243-19/+17
| | | | | | | | | | Since everything is in my control there's no need to parameterize include paths. It's a struggle to get make to run when it should. Lying that something is phony stops working when it's a dependency. Commands get unnecessarily run. Just fucking run recursive makes directly in the target that depends on them.
* .Kartik K. Agaram2021-11-241-3/+3
|
* consistent file opsKartik K. Agaram2021-11-241-6/+6
| | | | Now we're down to 1 real warning and 1 false positive.
* styleKartik K. Agaram2021-11-241-3/+3
|
* de-duplicate some words in the ReadmeKartik K. Agaram2021-11-241-4/+3
|
* renameKartik K. Agaram2021-11-241-7/+7
|
* indentKartik K. Agaram2021-11-241-32/+32
|
* .Kartik K. Agaram2021-11-231-0/+1
|
* indentKartik K. Agaram2021-11-234-51/+51
|
* consistent styleKartik K. Agaram2021-11-232-16/+23
|
* chess: tweak colors a bitKartik K. Agaram2021-11-231-4/+4
|
* chess: extract color parametersKartik K. Agaram2021-11-231-16/+16
|
* chess: extract a new functionKartik K. Agaram2021-11-231-2/+6
|
* chess: fix inconsistency in light piece colorKartik K. Agaram2021-11-231-2/+2
|
* .Kartik K. Agaram2021-11-231-4/+4
|
* clean up a warning and a bit of duplicationKartik K. Agaram2021-11-224-35/+2
| | | | | Now we have 2 probably-valid warnings caused by my edits, and 1 false-positive.
* standardize warning flags everywhereKartik K. Agaram2021-11-229-26/+23
| | | | | | | | | | I'd like to enable -Wextra as well, but that creates some false positives. I've at least made my changes clean w.r.t. -Wextra. Now we have 4 remaining warnings with gcc 9.3 that seem genuine. Need to fix those.
* .Kartik K. Agaram2021-11-221-13/+8
|
* drop a warning implied by -WallKartik K. Agaram2021-11-221-1/+1
|
* standardize CFLAGS in luasocketKartik K. Agaram2021-11-221-5/+4
|
* standardize CFLAGSKartik K. Agaram2021-11-221-1/+1
| | | | | Adding -Wpedantic creates a new warning. Leaving it alone for now: https://stackoverflow.com/questions/31526876/casting-when-using-dlsym
* standardize CFLAGS in luasecKartik K. Agaram2021-11-221-6/+6
| | | | | | What in the world is up with the $MYCFLAGS convention in these Lua makefiles? I don't know, but I'm going to leave it undisturbed as far as possible.
* standardize on gccKartik K. Agaram2021-11-221-1/+1
| | | | cc and gcc are identical on my system. But why rely on that.
* chess: make white pieces red for legibilityKartik K. Agaram2021-11-221-8/+10
|
* delete final vestiges of embedded luasocketKartik K. Agaram2021-11-227-243/+7
|
* delete most of the embedded luasocket in luasecKartik K. Agaram2021-11-2212-1545/+8
| | | | Hilariously, I wasn't linking against it in the first place.
* clarify implications for the `require` keywordKartik K. Agaram2021-11-221-0/+5
|
* .Kartik K. Agaram2021-11-221-1/+1
|
* showcase other apps in the ReadmeKartik K. Agaram2021-11-221-0/+17
|
* link to video in ReadmeKartik K. Agaram2021-11-221-1/+1
| | | | | I played with inlining video files, but this seems like the sweet spot: accessible video that isn't in the reader's face.
* chesstv: light colored square on bottom rightKartik K. Agaram2021-11-221-2/+2
| | | | 1-based indexing is a hassle.
* luasec: fix 'make clean'Kartik K. Agaram2021-11-221-3/+3
|
* chesstv.tlv: render clocksKartik K. Agaram2021-11-211-0/+8
|
* chesstv.tlv: looking much betterKartik K. Agaram2021-11-211-24/+55
| | | | | | | | | - square colors are slightly different - moves are now highlighted In the process I found lots of bugs in the rendering, and gave up on supporting adjustable orientation. Just always keep White's side at the bottom.
generated by cgit-pink 1.4.1-2-gfad0 (git 2.36.2.497.gbbea4dcf42) at 2024-11-14 06:56:55 +0000