about summary refs log tree commit diff stats
Commit message (Collapse)AuthorAgeFilesLines
...
* another fix for colorsKartik K. Agaram2021-12-031-2/+2
| | | | | I'd assumed that assume_default_colors updates fg/bg -1, but it doesn't. Looks like I can't ever use -1 colors.
* elaborate a little more on install instructionsKartik K. Agaram2021-12-032-3/+29
| | | | | Thanks to Mariano Guerra for the Nix command, and to Konrad Hinsen for the Guix command.
* support the comment/uncomment hotkey on MacsKartik K. Agaram2021-12-032-2/+3
| | | | | | | ^/ works on Linux but not on Mac ^- emits the same character code on Mac ^_ seems to be the underlying character code, and works on both ctrl-7 also emits the same character code
* less ambiguous menusKartik K. Agaram2021-12-032-9/+9
| | | | | Doesn't make sense to use '/' as a delimiter when we have hotkeys involving '/'.
* get rid of `Esc` hotkeyKartik K. Agaram2021-12-033-10/+9
| | | | | For a variety of historical reasons, terminals pause every time you press `Esc`. Let's get rid of that lag.
* typosKartik K. Agaram2021-12-031-3/+3
|
* experimenting with different keysKartik K. Agaram2021-12-031-0/+2
| | | | | | | | | | | | | | On a Thinkpad X13, the `delete` key emits `^[[3~` outside of Teliva. Within Teliva, ncurses converts it to character code 330 (0x14a), which it fails to recognize as KEY_BACKSPACE. Why? My backspace is converted to character code 263, which ncurses does recognize as KEY_BACKSPACE. ctrl-h is character code 8. Both 330 and 263 are valid Unicode code points, which feels really ugly and ambiguous.
* stop showing frequent save messagesKartik K. Agaram2021-12-031-1/+1
|
* show ^h in a couple more menusKartik K. Agaram2021-12-031-0/+2
|
* improve support for backspaceKartik K. Agaram2021-12-034-19/+24
| | | | | | | I still don't understand the entire state space here, so I'm trying to err on the side of improving discoverability of the `ctrl-h` escape hatch. Without requiring too wide a window to show all hotkeys on the menu.
* error message when no app is providedKartik K. Agaram2021-12-031-194/+6
| | | | Also strip out a bunch of Lua's commandline parsing.
* .Kartik K. Agaram2021-12-031-2/+3
|
* describe the manual process to obtain a dark bgKartik K. Agaram2021-12-031-0/+8
| | | | https://github.com/akkartik/teliva/issues/1
* legible colors across all terminal configurationsKartik K. Agaram2021-12-031-1/+1
| | | | | | | | | | | | | So far I've been trying to make Teliva follow the default colorscheme of the terminal, but that easily ends up with illegible color combinations. New plan: always start with a light background within Teliva. People who want a dark background will currently need to mess with C sources. This should somewhat fix https://github.com/akkartik/teliva/issues/1. It's still not clear whether the default should be a dark or light background. While dark background is more common in terminals, I believe newcomers to terminals will prefer a light background. Then again, I'm biased since I use a light background in my terminals.
* show state of screen on runtime errorKartik K. Agaram2021-12-031-0/+7
| | | | This is essential when debugging.
* .Kartik K. Agaram2021-12-031-1/+1
|
* extract a helperKartik K. Agaram2021-12-031-18/+32
|
* more speculatively efficient advent.tlvKartik K. Agaram2021-12-021-6/+3
|
* fix a slight portability issue, maybeKartik K. Agaram2021-12-021-1/+1
| | | | | | | | When installing using NixOS[1], the screen looks wrong. It looks like attrset(A_NORMAL) does not undo color changes with some versions of dependencies. [1] https://github.com/marianoguerra/marianoguerra.github.io/blob/master/advent-of-future-of-code/days/day-02.md
* stop inserting ctrl- keys into programsKartik K. Agaram2021-11-301-4/+2
|
* fix advent.tlvKartik K. Agaram2021-11-301-2/+2
| | | | Thanks sejo.
* some little shortcuts for Advent of CodeKartik K. Agaram2021-11-301-0/+159
| | | | https://archive.org/details/akkartik-teliva-2021-11-30
* better cross-platform backspace supportKartik K. Agaram2021-11-302-4/+10
| | | | | | | | I wish I could just hide KEY_BACKSPACE and prevent myself from using it by accident. Then again, I'm not making this smarts available in Teliva programs themselves. Just for the Teliva environment.
* kilo bugfix: syntax highlight final word in lineKartik K. Agaram2021-11-291-1/+1
| | | | | Kilo likely never ran into this because it's only been tested on C, which uses semi-colons at the end of each statement.
* gotcha: silent string concatenationKartik K. Agaram2021-11-291-1/+1
|
* .Kartik K. Agaram2021-11-291-7/+7
|
* a couple more global curses bindingsKartik K. Agaram2021-11-291-0/+3
|
* fix regression in showing error messagesKartik K. Agaram2021-11-291-4/+4
|
* .Kartik K. Agaram2021-11-291-2/+0
|
* why not keep manual tests in the repo?Kartik K. Agaram2021-11-291-0/+15
|
* let people fix bad images from within TelivaKartik K. Agaram2021-11-292-12/+28
| | | | | | | | | Short of syntax errors that keep us from parsing the teliva_program table, we should now be able to recover gracefully from everything. Yesterday I started to try to add this to load_definitions before realizing most errors are only noticed while running `main`. But I didn't think of recovering from the docall of `main` until this morning.
* redo uncommentKartik K. Agaram2021-11-281-5/+6
| | | | It was printing a phantom null at end of line on screen.
* auto-indentKartik K. Agaram2021-11-281-1/+7
|
* tab key: always insert two spacesKartik K. Agaram2021-11-281-0/+5
|
* hide some 'advanced' hotkeys to support narrow windowsKartik K. Agaram2021-11-281-4/+0
|
* ctrl-/ to comment/uncomment lineKartik K. Agaram2021-11-282-0/+28
|
* ctrl-u/ctrl-k to make editing a bit more ergonomicKartik K. Agaram2021-11-282-1/+18
|
* special indent settings for kiloKartik K. Agaram2021-11-281-0/+3
|
* indentKartik K. Agaram2021-11-281-40/+40
|
* mac backspace attempt 3Kartik K. Agaram2021-11-281-1/+1
|
* fix half-assed mac os backspace commitKartik K. Agaram2021-11-282-4/+4
|
* sacrificing another LoC to ward off crashesKartik K. Agaram2021-11-281-0/+1
| | | | | | It makes me very nervous now that there's save_editor_state within editor event loop, when the editor could be editing notes. Things are slightly better than this morning, but this prototype still suxxors.
* editing notes sucks a little lessKartik K. Agaram2021-11-282-4/+10
| | | | | | I think I've gotten rid of all the segfaults, but it's still pretty messed up: if you hit ctrl-g and go edit some definition, it doesn't get saved. You're just storing the edit in the note.
* fix the bug described in commit cec57992b7Kartik K. Agaram2021-11-281-4/+12
|
* rename a fn and reorganize its responsibilitiesKartik K. Agaram2021-11-281-3/+3
|
* split a lumpy abstraction into two cleaner onesKartik K. Agaram2021-11-281-13/+19
| | | | | | | | | | | | | | I'm mindful of the way abstractions can create duplicate effort: https://flak.tedunangst.com/post/browser-ktrace-browsing == Kartik's SAD theorem As programs grow complex, you will be repeatedly forced to either: - maintain some State, - perform some computations Again, - or Duplicate some code. Here a small amount of duplication seems like the best alternative. Particularly since no syscalls are involved.
* purge abstraction hiding teliva_editor_bufferKartik K. Agaram2021-11-281-10/+5
|
* inline another functionKartik K. Agaram2021-11-282-8/+2
| | | | | I'm going to give up on hiding teliva_editor_buffer from kilo. It was taking too much knowledge of extern function prototypes on both sides.
* take one responsibility away from edit_imageKartik K. Agaram2021-11-281-4/+4
| | | | Also rename it appropriately.
* .Kartik K. Agaram2021-11-281-1/+1
|
generated by cgit-pink 1.4.1-2-gfad0 (git 2.36.2.497.gbbea4dcf42) at 2024-12-11 19:27:04 +0000