about summary refs log tree commit diff stats
path: root/text.lua
Commit message (Collapse)AuthorAgeFilesLines
* Merge lines.loveKartik K. Agaram2023-11-251-1/+8
|\
| * improved handling of other keyboard layoutsKartik K. Agaram2023-11-251-1/+8
| |
* | Merge lines.loveKartik K. Agaram2023-11-241-1/+9
|\|
| * bugfix: infinite loop inside a very narrow windowKartik K. Agaram2023-11-241-1/+3
| | | | | | | | | | | | I'm not sure this can trigger everywhere (I've only been able to exercise it in Lua Carousel), but it seems like a safety net worth having against future modifications by anybody.
| * establish a fairly fundamental invariantKartik K. Agaram2023-11-241-0/+6
| | | | | | | | | | | | | | This commit doesn't guarantee we'll always catch it. But if this invariant is violated, things can get quite difficult to debug. I found in the Lua Carousel fork that all the xpcalls I keep around were actively hindering my ability to notice this invariant being violated.
* | Merge lines.loveKartik K. Agaram2023-11-181-15/+14
|\|
| * audit all assertsKartik K. Agaram2023-11-181-23/+22
| | | | | | | | | | | | | | | | | | | | | | | | | | Each one should provide a message that will show up within LÖVE. Stop relying on nearby prints to the terminal. I also found some unnecessary ones. There is some potential here for performance regressions: the format() calls will trigger whether or not the assertion fails, and cause allocations. So far Lua's GC seems good enough to manage the load even with Moby Dick, even in some situations that caused issues in the past like undo.
* | Merge lines.loveKartik K. Agaram2023-07-311-14/+22
|\|
| * bugfix: search highlight straddling screen linesKartik K. Agaram2023-07-311-7/+8
| |
| * remove a duplicate print to screenKartik K. Agaram2023-07-311-6/+5
| | | | | | | | In addition to being more efficient, this will simplify the next bugfix.
| * extract a variableKartik K. Agaram2023-07-311-1/+2
| |
| * bugfix: highlight search patterns on the right lineKartik K. Agaram2023-07-311-2/+7
| | | | | | | | | | | | | | | | | | | | | | | | scenario: * position a wrapped line on screen * search for the word immediately after the point of wrapping Before this commit the word would be highlighted twice: - at the end of the first screen line - at the start of the second screen line Now it shows up at the right place.
| * hoist and duplicate a conditionalKartik K. Agaram2023-07-311-3/+5
| | | | | | | | | | | | I'm duplicating the bounds check when drawing cursor and search highlight because they're separate concerns and require subtly different logic.
| * improve a commentKartik K. Agaram2023-07-311-1/+1
| |
* | Merge lines.loveKartik K. Agaram2023-06-041-0/+15
|\|
| * bugfix: inscript's bugKartik K. Agaram2023-06-041-0/+15
| | | | | | | | | | | | | | | | | | | | To fix this I have to first stop incrementally updating screen_bottom1 in the middle of a frame. Now it always has a good value from the end of a frame. I'm also running into some limitations in the test I'd ideally like to write (that are documented in a comment), but I still get some sort of automated test for this bugfix.
* | Merge lines.loveKartik K. Agaram2023-05-141-0/+1
|\|
| * add an assertKartik K. Agaram2023-05-141-0/+1
| | | | | | | | | | I added this to catch a rare bug. I've had it locally for a few weeks now without hitting it. Doesn't hurt to publish it.
* | Merge lines.loveKartik K. Agaram2023-05-061-1/+3
|\|
| * bugfix: never use utf8 pos in string.subKartik K. Agaram2023-05-061-1/+3
| | | | | | | | | | | | This is a violation of an existing rule in Manual_tests.md. The following command weakly suggests there aren't any others: grep ':sub(' *.lua |grep pos
| * remove some support for long lines from source editorKartik K. Agaram2023-04-191-0/+3
| | | | | | | | | | | | | | | | | | | | | | | | A code editor is unlikely to need support for extremely long lines. And that kind of scroll is jarring anyway in a code editor. We don't read code like a novel, and less scroll per page implies more scrolling work. I'd gotten rid of this functionality and the test for it [1] back in the spokecone fork, but only took out the test when first pulling it into the source editor. [1] test_pagedown_often_shows_start_of_wrapping_line
* | Merge lines.loveKartik K. Agaram2023-04-081-6/+5
|\|
| * rename a variableKartik K. Agaram2023-04-081-6/+5
| |
* | Merge lines.loveKartik K. Agaram2023-04-031-4/+3
|\|
| * switch source side to new screen-line-based renderKartik K. Agaram2023-04-031-1/+0
| | | | | | | | Also copy over the implementation of links from pensieve.love.
| * change cursor bounds check slightlyKartik K. Agaram2023-04-021-1/+1
| | | | | | | | | | | | This doesn't affect this fork directly, but it's a bad idea to assume the _app_ is always going to be doing just what a particular subsystem (here, the text editor in edit.lua+text.lua) is doing.
| * streamline the interface for Text.drawKartik K. Agaram2023-04-021-2/+2
| |
* | Merge lines.loveKartik K. Agaram2023-04-021-90/+53
|\|
| * avoid saving fragments in linesKartik K. Agaram2023-04-011-67/+46
| | | | | | | | | | | | | | Now we render lines one screen line at a time rather than one word at a time. I can't port the source side just yet; I need to fix hyperlinks first..
| * start thinking of compute_fragments as a detailKartik K. Agaram2023-04-011-1/+1
| | | | | | | | | | | | | | | | | | | | I think all we need to maintain is the populate_screen_line_starting_pos array. It's easy to render screen lines one by one from it, and we'll only ever construct one additional screen line at a time. I'd hoped to delete other calls to Text.populate_screen_line_starting_pos, but it turns out we need to update it when editing sometimes. Give up on that for now; it's a no-op if not needed.
| * stop creating a singleton table for every wordKartik K. Agaram2023-04-011-10/+10
| |
| * clean up some debug printsKartik K. Agaram2023-04-011-8/+0
| | | | | | | | | | It's starting to become apparent just how little line_cache.fragments does for me now. Let's see if we can get rid of it entirely.
| * no more Text allocationsKartik K. Agaram2023-04-011-14/+8
| | | | | | | | Is it just my imagination, or does the app feel lighter and more fluffy?
| * App.width can no longer take a TextKartik K. Agaram2023-04-011-11/+8
| | | | | | | | | | In the process I discovered the horrible fact that Text.x allocates a new Text. And it gets called (just once, thank goodness) on every single frame.
| * bugfix: naming pointsKartik K. Agaram2023-03-261-0/+1
| |
* | Merge lines.loveKartik K. Agaram2023-03-171-11/+15
|\|
| * more bugfixKartik K. Agaram2023-03-171-1/+1
| | | | | | | | Don't crash on showing the log browser.
| * bugfixKartik K. Agaram2023-03-171-9/+14
| | | | | | | | Thanks Mikoláš Štrajt.
| * get rid of all bifold textKartik K. Agaram2023-03-171-1/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | It's just uneconomic to maintain given how little I've used it. I have a bug right now and no time to port the bugfix to all the complexities of the B side. I briefly considered tossing out the entire source editor. But I _have_ been using it to browse logs across sessions. The live editor doesn't quite cover all my use cases just yet. We now have duplication in the source editor only for: * syntax highlighting * hyperlinking [[WikiWords]] * ability to hide cursor (when showing file browser or Focus is in log browser)
* | Merge lines.loveKartik K. Agaram2023-01-311-1/+1
|\|
| * bugfix: up arrow when line above is a drawingKartik K. Agaram2023-01-311-1/+1
| | | | | | | | This bug was introduced in commit 528c64d690 on 2022-09-05 :/
* | Merge lines.loveKartik K. Agaram2023-01-131-0/+24
|\|
| * reduce use of rfindKartik K. Agaram2023-01-131-0/+24
| |
* | 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
generated by cgit-pink 1.4.1-2-gfad0 (git 2.36.2.497.gbbea4dcf42) at 2024-12-03 13:47:29 +0000