about summary refs log tree commit diff stats
path: root/text.lua
Commit message (Collapse)AuthorAgeFilesLines
* Merge lines.loveKartik K. Agaram2022-12-231-3/+3
|\
| * make love event names consistentKartik K. Agaram2022-12-231-3/+3
| | | | | | | | | | I want the words to be easy to read, and to use a consistent tense. update and focus seem more timeless; let's make everything like those.
* | Merge lines.loveKartik K. Agaram2022-09-061-1/+0
|\|
| * support selections in the source editorKartik K. Agaram2022-09-061-1/+0
| | | | | | | | | | I've only tested side A so far, and included a statement of how I want side B to behave.
* | Merge lines.loveKartik K. Agaram2022-09-051-10/+12
|\|
| * support drawings in the source editorKartik K. Agaram2022-09-051-17/+22
| |
| * editing source code from within the appKartik K. Agaram2022-09-031-5/+0
| | | | | | | | | | integrated from pong.love via text.love: https://merveilles.town/@akkartik/108933336531898243
* | stray edit from source_text.luaKartik K. Agaram2022-09-031-1/+0
| |
* | editing source code from within the appKartik K. Agaram2022-09-031-5/+1
| | | | | | | | integrated from pong.love: https://merveilles.town/@akkartik/108933336531898243
* | Merge lines.loveKartik K. Agaram2022-08-231-1/+13
|\|
| * set color for each fragmentKartik K. Agaram2022-08-231-1/+1
| | | | | | | | | | In general it seems like good practice to minimize assumptions about the current color.
| * helper: trimming whitespace from stringsKartik K. Agaram2022-08-231-0/+12
| |
* | Merge lines.loveKartik K. Agaram2022-08-191-4/+4
|\|
| * fix a nameKartik K. Agaram2022-08-191-4/+4
| |
* | Merge lines.loveKartik K. Agaram2022-08-181-2/+2
|\|
| * couple of accidental globalsKartik K. Agaram2022-08-181-2/+2
| | | | | | | | Luckily they didn't bite me yet.
* | Merge lines.loveKartik K. Agaram2022-08-181-49/+36
|\|
| * get rid of some ridiculous codeKartik K. Agaram2022-08-181-15/+5
| | | | | | | | | | | | I guess I wrote it before I settled into the idiom of: * first change cursor * then scroll if necessary
| * spurious argsKartik K. Agaram2022-08-181-18/+18
| |
| * dead codeKartik K. Agaram2022-08-181-2/+0
| |
| * generalize a functionKartik K. Agaram2022-08-181-9/+10
| |
| * extract a variableKartik K. Agaram2022-08-181-2/+3
| |
| * simplifyKartik K. Agaram2022-08-181-4/+1
| |
* | Merge lines.loveKartik K. Agaram2022-08-171-4/+5
|\|
| * move caching behavior inside compute_fragmentsKartik K. Agaram2022-08-171-6/+6
| |
| * remove some unnecessary workKartik K. Agaram2022-08-171-1/+3
| |
* | Merge lines.loveKartik K. Agaram2022-08-171-9/+9
|\|
| * standardize scroll check in a few placesKartik K. Agaram2022-08-171-3/+3
| | | | | | | | | | | | | | | | | | | | | | | | I'm taking some lessons from pensieve.love here. It seem like specific pixel thresholds don't matter too much for plain lines.love. I'd probably feel safer if I just used Text.cursor_out_of_screen in these places, but it means we draw the screen twice for most events[1]. Let's see if we can get by with the current approach. [1] Or we have to start scheduling things for the next draw, which is more complex to orchestrate.
| * simplify cursor-on-screen checkKartik K. Agaram2022-08-171-6/+6
| |
* | Merge lines.loveKartik K. Agaram2022-08-171-5/+5
|\|
| * swap return valuesKartik K. Agaram2022-08-171-5/+5
| |
* | Merge lines.loveKartik K. Agaram2022-08-171-2/+0
|\|
| * obsolete commentKartik K. Agaram2022-08-161-2/+0
| |
* | Merge lines.loveKartik K. Agaram2022-08-151-27/+27
|\| | | | | | | | | (I'm going to change the format of these commits to be more useful in the presence of more than one level of upstream.)
| * moveKartik K. Agaram2022-08-151-28/+28
| |
* | Merge upstreamKartik K. Agaram2022-08-151-8/+2
|\|
| * drop some unnecessary callsKartik K. Agaram2022-08-151-6/+0
| |
| * stop confusingly reading a globalKartik K. Agaram2022-08-151-2/+2
| | | | | | | | | | | | | | The way Text.draw is called by edit.draw, we know it'll never be called for lines above screen_top1.line. Comparing every line on screen with screen_top1 makes no sense. The intent is really just to compare with screen_top1 only for the first line, and otherwise to ignore this check.
* | bring back a level of wrappingKartik K. Agaram2022-08-151-43/+43
| | | | | | | | | | Many projects will require the ability to add metadata to lines, so let's not drop that.
* | new fork: rip out drawing supportKartik K. Agaram2022-08-141-150/+78
|/
* bugfix: handle drawings when updating screen topKartik K. Agaram2022-08-111-0/+1
|
* renameKartik K. Agaram2022-08-111-24/+24
|
* bugfix: pagedown was sometimes bouncing upKartik K. Agaram2022-08-101-1/+1
|
* bugfix: backspace from start of final lineKartik K. Agaram2022-08-101-1/+5
|
* unnecessary argsKartik K. Agaram2022-08-101-1/+1
|
* click to the left of a lineKartik K. Agaram2022-07-291-2/+1
|
* bugfix: searchKartik K. Agaram2022-07-211-1/+1
| | | | | Broken since commit 188bbc73 9 days ago :/ At least we have a test for it now.
* use line cache for drawings as wellKartik K. Agaram2022-07-201-26/+26
|
* bugfix: where cursor is drawnKartik K. Agaram2022-07-201-4/+11
| | | | | | | The published version of lines.love was broken for almost an hour. The cursor would render one position to the right of where it really is. To fix it, this commit rolls back 26ba6e4e5a71. There doesn't seem a good way to test it.
* .Kartik K. Agaram2022-07-201-0/+2
|
generated by cgit-pink 1.4.1-2-gfad0 (git 2.36.2.497.gbbea4dcf42) at 2024-12-25 18:21:32 +0000