about summary refs log tree commit diff stats
Commit message (Collapse)AuthorAgeFilesLines
* 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.
* chess: better colorsKartik K. Agaram2021-11-211-6/+38
|
* almost done with chess appKartik K. Agaram2021-11-211-2/+111
| | | | It's still not very legible.
* figured out streaming http!Kartik K. Agaram2021-11-211-3/+22
| | | | http://lua-users.org/wiki/FiltersSourcesAndSinks
* .Kartik K. Agaram2021-11-211-4/+4
|
* more thinking around compatibility and governanceKartik K. Agaram2021-11-211-28/+35
|
* include new dependency in ReadmeKartik K. Agaram2021-11-211-0/+1
|
* https now working!Kartik K. Agaram2021-11-2135-10/+5641
| | | | | | | | Still extremely ugly: - I've inlined all the namespaces under ssl, so you need to know that context and config are related to ssl. - luasec comes with its own copy of luasocket. I haven't deduped that yet.
* basic http requests starting to workKartik K. Agaram2021-11-2114-109/+92
| | | | | In the process we're starting to load almost all of luasocket by default. And everything is working as expected, no unpleasant surprises.
* start on HTTP clientKartik K. Agaram2021-11-214-36/+9
|
* now. we. have. JSON.Kartik K. Agaram2021-11-214-0/+400
| | | | Completely unmodified from upstream.
* .Kartik K. Agaram2021-11-211-2/+2
|
* first glimmers of networking workingKartik K. Agaram2021-11-212-0/+29
|
* 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 :/
generated by cgit-pink 1.4.1-2-gfad0 (git 2.36.2.497.gbbea4dcf42) at 2024-11-14 22:54:18 +0000