about summary refs log tree commit diff stats
Commit message (Collapse)AuthorAgeFilesLines
* things seem to feel snappier nowKartik K. Agaram2022-06-101-6/+2
| | | | | However, I think a lot of the benefit comes from just turning JIT off. Turning it on is still noticably sluggish.
* stop handling nil screen_line_starting_pos everywhereKartik K. Agaram2022-06-102-24/+6
| | | | Things seem to be working..
* this fixes the immediate regressionKartik K. Agaram2022-06-101-19/+17
|
* stop repeatedly checking for line wrappingKartik K. Agaram2022-06-101-7/+8
| | | | | | We have a regression since we started reclaiming love Text fragments more aggressively in commit 69c5d844ccc. Pressing pageup no longer knows about any line's screen lines. Not fixed yet.
* slight reorg in ReadmeKartik K. Agaram2022-06-101-2/+4
|
* more precise scroll on pasteKartik K. Agaram2022-06-101-19/+4
|
* faster pasteKartik K. Agaram2022-06-102-13/+11
| | | | | We don't need to perform the scroll calculations after inserting every single character from the clipboard.
* revert previous commitKartik K. Agaram2022-06-101-5/+15
|
* experiment: extremely precise scrolling on pasteKartik K. Agaram2022-06-101-15/+5
| | | | But this is too slow.
* clean up memory leak experimentsKartik K. Agaram2022-06-102-517/+0
|
* while we're at it, undo naming pointsKartik K. Agaram2022-06-101-0/+2
|
* set current_drawing_index with current_drawingKartik K. Agaram2022-06-101-3/+6
|
* include drawing index in a few placesKartik K. Agaram2022-06-101-15/+15
|
* .Kartik K. Agaram2022-06-101-1/+1
|
* stop saving the entire file when modifying drawingsKartik K. Agaram2022-06-103-11/+10
| | | | Now we just disallow that entirely.
* undo creating new drawingsKartik K. Agaram2022-06-102-1/+8
|
* extract scrolling logic out of insert_at_cursorKartik K. Agaram2022-06-102-6/+18
|
* extract scrolling logic out of insert_returnKartik K. Agaram2022-06-102-4/+6
|
* remove some memory leaks from rendered fragmentsKartik K. Agaram2022-06-105-0/+2672
| | | | | | | | | | | | | | | All signs so far seem to be that CPU is cheap for this application, but memory is expensive. It's easy to get sluggish if the GC comes on. After some experiments using https://github.com/yaukeywang/LuaMemorySnapshotDump, one source of memory leaks is rendered fragments (https://love2d.org/wiki/Text objects). I need to render text in approximately word-sized fragments to mostly break lines more intelligently at word boundaries. I've attached the files I used for my experiments (suffixed with a '.') There's definitely still a leak in fragments. The longer I edit, the more memory goes to them.
* avoid some string concatenationsKartik K. Agaram2022-06-101-6/+6
| | | | | | | | file:write can write multiple args one after another; no need to concatenate them first. I'm starting to pay attention to memory usage after the experience of turning off the JIT.
* include a unit testKartik K. Agaram2022-06-091-0/+17
|
* bugfix: cut (C-x) without first selecting anythingKartik K. Agaram2022-06-092-0/+5
|
* fix a corner case when selecting textKartik K. Agaram2022-06-092-9/+51
| | | | | The hard part here is keeping click-drag selection working (without pressing and holding shift).
* moveKartik K. Agaram2022-06-091-4/+4
|
* .Kartik K. Agaram2022-06-091-4/+2
|
* test both ways of selecting text with mouseKartik K. Agaram2022-06-091-4/+25
|
* experiment: blinking cursorKartik K. Agaram2022-06-092-3/+10
| | | | | | | | | I've tried to keep the time period of the blinking similar to my terminal. Honestly I'm no longer sure if any of my experiments are showing a statistically significant result. Let's see how it feels over a period of time.
* the problem is that the cursor can occlude textKartik K. Agaram2022-06-091-1/+1
| | | | | | | And anything we do to reduce the occlusion also makes the cursor harder to acquire. I suppose this is why we need the blink.
* make the cursor a little thickerKartik K. Agaram2022-06-091-1/+1
| | | | | | | I'm testing this by moving the cursor around with my eyes closed, then starting a stopwatch as I open my eyes. This seems to help a bit. I'm able to acquire the cursor in 2s. At least the 10s outliers I used to have with the circle or thin line don't seem to be happening.
* experiment: line cursorKartik K. Agaram2022-06-091-1/+1
|
* fix contact linkKartik K. Agaram2022-06-091-1/+1
|
* experiment: turn off JITKartik K. Agaram2022-06-091-0/+5
| | | | This seems to speed up copy! What does it slow down?
* moveKartik K. Agaram2022-06-091-6/+6
|
* speeding up copy, attempt 1Kartik K. Agaram2022-06-091-4/+4
| | | | | | | | | | | | | | Problem: repeatedly copying (relatively large) sections of text quickly makes the app sluggish until it has to be killed. (Thanks John Blommers for the report.) When I instrument with prints, the sluggishness seems to happen in random draw() calls many times after I perform the copy. I don't know for sure, but I'm initially checking if the cause is garbage generated by repeated string concatenation. This attempt doesn't seem to make any difference.
* more defensive resize handlingKartik K. Agaram2022-06-072-2/+27
| | | | Thanks John Blommers for the report!
* forgot to commit documentation for the commandline argKartik K. Agaram2022-06-071-0/+10
|
* first commandline arg: window dimensionsKartik K. Agaram2022-06-071-8/+33
| | | | Hopefully there won't be too many others.
* use app name in window titleKartik K. Agaram2022-06-071-1/+1
|
* clearer discription of how to run lines.loveKartik K. Agaram2022-06-071-5/+22
|
* a likely source of issuesKartik K. Agaram2022-06-071-0/+4
|
* warn on unused commandline argsKartik K. Agaram2022-06-071-0/+4
|
* obsolete commentKartik K. Agaram2022-06-071-1/+0
|
* extract a functionKartik K. Agaram2022-06-071-11/+14
|
* allow the window to be resizedKartik K. Agaram2022-06-071-2/+13
| | | | | | This still isn't ideal. On my Linux laptop for some reason the window receives a signal to maximize itself soon after (but sometime after) the program starts.
* freudian typoKartik K. Agaram2022-06-071-1/+1
|
* fix a crashKartik K. Agaram2022-06-061-1/+3
| | | | | This one isn't worth debugging. We know how to recreate this data on demand.
* flesh out ReadmeKartik K. Agaram2022-06-061-0/+49
|
* another known issueKartik K. Agaram2022-06-061-4/+4
|
* autosave on cut/pasteKartik K. Agaram2022-06-051-0/+2
|
* additional logging for an active bugKartik K. Agaram2022-06-051-1/+5
|
generated by cgit-pink 1.4.1-2-gfad0 (git 2.36.2.497.gbbea4dcf42) at 2024-11-25 18:29:41 +0000