about summary refs log tree commit diff stats
path: root/src
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
|
* renameKartik K. Agaram2021-11-241-7/+7
|
* indentKartik K. Agaram2021-11-241-32/+32
|
* 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.
* 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.
* luasec: fix 'make clean'Kartik K. Agaram2021-11-221-3/+3
|
* https now working!Kartik K. Agaram2021-11-2134-9/+5640
| | | | | | | | 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-2113-108/+75
| | | | | In the process we're starting to load almost all of luasocket by default. And everything is working as expected, no unpleasant surprises.
* now. we. have. JSON.Kartik K. Agaram2021-11-212-0/+390
| | | | Completely unmodified from upstream.
* 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
|
generated by cgit-pink 1.4.1-2-gfad0 (git 2.36.2.497.gbbea4dcf42) at 2024-11-14 23:16:28 +0000