| Commit message (Collapse) | Author | Age | Files | Lines | ||
|---|---|---|---|---|---|---|
| ... | ||||||
| * | use header everywhere | Kartik K. Agaram | 2021-11-28 | 1 | -3/+3 | |
| | | ||||||
| * | unused variable | Kartik K. Agaram | 2021-11-28 | 1 | -1/+0 | |
| | | ||||||
| * | standardize filenames that teliva strews on disk | Kartik K. Agaram | 2021-11-28 | 2 | -26/+26 | |
| | | | | | | We still need a proper story for file system side effects. But it's not time yet for sandboxing considerations. Soon, but not yet. | |||||
| * | restore editor state from snapshot | Kartik K. Agaram | 2021-11-28 | 2 | -1/+62 | |
| | | ||||||
| * | make look_up_definition more composable | Kartik K. Agaram | 2021-11-28 | 1 | -7/+12 | |
| | | ||||||
| * | save a snapshot of editor state across restarts | Kartik K. Agaram | 2021-11-28 | 2 | -1/+14 | |
| | | | | | | | | | | | | | | | | | We're not using this yet. I agonized over this decision for several weeks. Is Teliva's need to restart with execve an utter hack or a good thing? I'm leaning towards the latter. Constantly exercising the initial flow makes Teliva more crash-only. We can build Steve Yegge's idea of immortality (http://steve-yegge.blogspot.com/2007/01/pinocchio-problem.html) out of crash-only primitives, just by making reboots instantaneous. But focusing directly on immortality tends to compromise crash-only by exercising it more rarely. One other issue this brings up: loading these Lua tables from disk is a vector for arbitrary code execution. I need to fix these when I get to sandboxing. | |||||
| * | more salient concept of 'views' | Kartik K. Agaram | 2021-11-28 | 1 | -4/+4 | |
| | | ||||||
| * | fix backspace on Mac | Kartik K. Agaram | 2021-11-28 | 2 | -1/+6 | |
| | | | | | | I'm deliberately restricting this incompatibility to the editor environment for now. | |||||
| * | editor hotkeys: sol/eol | Kartik K. Agaram | 2021-11-28 | 2 | -4/+20 | |
| | | | | | | I'm growing attached to ^e, so mildly breaking with convention there. Perhaps this is a bad idea. | |||||
| * | pass some CFLAGS at least to libcurses | Kartik K. Agaram | 2021-11-27 | 1 | -3/+3 | |
| | | | | | | My Makefiles are an utter mess. Unclear how to reconcile staying close to upstream with being clean in isolation. | |||||
| * | . | Kartik K. Agaram | 2021-11-27 | 1 | -0/+1 | |
| | | ||||||
| * | one final issue building on Mac OS X | Kartik K. Agaram | 2021-11-27 | 1 | -2/+2 | |
| | | ||||||
| * | now building on OpenBSD | Kartik K. Agaram | 2021-11-27 | 3 | -14/+15 | |
| | | | | | Still emitting a bunch of warnings on OpenBSD, though. | |||||
| * | select C99 in luasec | Kartik K. Agaram | 2021-11-27 | 2 | -3/+3 | |
| | | | | | | | I can't select C99 in luasocket, because I don't know how to include the definition of struct timespec. All this fucking complexity. But hopefully things will build on OpenBSD now. | |||||
| * | select C99 standard | Kartik K. Agaram | 2021-11-27 | 3 | -5/+10 | |
| | | ||||||
| * | clean up luasocket build file | Kartik K. Agaram | 2021-11-27 | 1 | -142/+15 | |
| | | | | | | | Teliva is never intended to be "installed" somewhere. Just work inside its directory and separately share the .tlv files you create. (Though I don't yet have a good flow for starting a new .tlv file.) | |||||
| * | . | Kartik K. Agaram | 2021-11-27 | 1 | -6/+6 | |
| | | ||||||
| * | fix build on Mac | Kartik K. Agaram | 2021-11-27 | 3 | -2/+7 | |
| | | ||||||
| * | starting to test compilation on Mac and BSD. | Kartik K. Agaram | 2021-11-27 | 1 | -2/+2 | |
| | | | | | | | | | For starters, put Linux-specific stuff in a Linux-specific target. By not resetting MYCFLAGS and MYLDFLAGS, I'm unnecessarily passing in -DLUA_USE_LINUX. But that'll make it easier to get things running on Mac and BSD. | |||||
| * | bugfix: emit legal Lua representation | Kartik K. Agaram | 2021-11-26 | 1 | -1/+1 | |
| | | ||||||
| * | support space/backspace in recent changes view | Kartik K. Agaram | 2021-11-26 | 1 | -6/+8 | |
| | | ||||||
| * | standardize indent | Kartik K. Agaram | 2021-11-26 | 1 | -4/+4 | |
| | | ||||||
| * | colorize comments in recent changes | Kartik K. Agaram | 2021-11-26 | 1 | -0/+4 | |
| | | ||||||
| * | support notes on edits | Kartik K. Agaram | 2021-11-26 | 1 | -2/+38 | |
| | | | | | | Unlike both conventional version control and wiki history, I'm planning to always allow modifying commit messages. | |||||
| * | periodic cleanup of warnings | Kartik K. Agaram | 2021-11-26 | 1 | -3/+3 | |
| | | ||||||
| * | . | Kartik K. Agaram | 2021-11-26 | 1 | -4/+3 | |
| | | ||||||
| * | . | Kartik K. Agaram | 2021-11-26 | 1 | -1/+1 | |
| | | ||||||
| * | don't mislead immediately after undo | Kartik K. Agaram | 2021-11-26 | 1 | -1/+7 | |
| | | ||||||
| * | . | Kartik K. Agaram | 2021-11-26 | 1 | -1/+0 | |
| | | ||||||
| * | more obvious serialization of undo events | Kartik K. Agaram | 2021-11-26 | 1 | -0/+4 | |
| | | ||||||
| * | render undo events | Kartik K. Agaram | 2021-11-26 | 1 | -0/+8 | |
| | | ||||||
| * | start processing undo events | Kartik K. Agaram | 2021-11-26 | 1 | -0/+14 | |
| | | ||||||
| * | start recording undo events in timeline | Kartik K. Agaram | 2021-11-26 | 1 | -6/+30 | |
| | | | | | We're not using or rendering them yet. | |||||
| * | save timestamp on change; show in recent changes | Kartik K. Agaram | 2021-11-26 | 1 | -2/+20 | |
| | | ||||||
| * | . | Kartik K. Agaram | 2021-11-26 | 1 | -0/+1 | |
| | | ||||||
| * | clean up traces of an old experiment | Kartik K. Agaram | 2021-11-26 | 1 | -2/+2 | |
| | | ||||||
| * | add support for metadata in Teliva programs | Kartik K. Agaram | 2021-11-26 | 1 | -12/+26 | |
| | | | | | They don't have any semantics yet. We just ignore them for now. | |||||
| * | undo to a specific point | Kartik K. Agaram | 2021-11-26 | 1 | -4/+12 | |
| | | | | | Still highly experimental. I'm not persisting state yet. | |||||
| * | standardize screen headings | Kartik K. Agaram | 2021-11-26 | 1 | -1/+5 | |
| | | ||||||
| * | start of 'recent changes' screen | Kartik K. Agaram | 2021-11-26 | 1 | -0/+102 | |
| | | | | | | | | | | I'm still unclear on precisely what the experience should be here. We probably don't need all of a version control system. The goal is just to be able to answer the question, "what did I change recently that caused things to break?" For now let's just start with letting people see past versions. | |||||
| * | eliminate tail call using goto | Kartik K. Agaram | 2021-11-26 | 1 | -1/+2 | |
| | | ||||||
| * | clean up terminal in a specific situation | Kartik K. Agaram | 2021-11-26 | 1 | -7/+6 | |
| | | | | | | | | | | The problem: if ever I hit ctrl-e to go to the big picture view and then hit Esc to go back to running the app, my terminal was messed up after exiting the app. Why did I even have this gunk? Perhaps it dates from the time when kilo was emitting raw escape sequences rather than using ncurses. | |||||
| * | dedup an enum | Kartik K. Agaram | 2021-11-26 | 3 | -24/+26 | |
| | | ||||||
| * | . | Kartik K. Agaram | 2021-11-26 | 1 | -2/+2 | |
| | | ||||||
| * | . | Kartik K. Agaram | 2021-11-26 | 1 | -2/+2 | |
| | | ||||||
| * | extract a function | Kartik K. Agaram | 2021-11-25 | 1 | -10/+18 | |
| | | ||||||
| * | more stack hygiene | Kartik K. Agaram | 2021-11-25 | 1 | -0/+2 | |
| | | ||||||
| * | one more curses binding | Kartik K. Agaram | 2021-11-25 | 1 | -0/+1 | |
| | | ||||||
| * | libraries don't need Lua's `#define`s and whatnot | Kartik K. Agaram | 2021-11-25 | 1 | -2/+2 | |
| | | ||||||
| * | . | Kartik K. Agaram | 2021-11-25 | 1 | -1/+1 | |
| | | ||||||