| Commit message (Collapse) | Author | Age | Files | Lines | |
|---|---|---|---|---|---|
| * | undo creating new drawings | Kartik K. Agaram | 2022-06-10 | 2 | -1/+8 |
| | | |||||
| * | extract scrolling logic out of insert_at_cursor | Kartik K. Agaram | 2022-06-10 | 2 | -6/+18 |
| | | |||||
| * | extract scrolling logic out of insert_return | Kartik K. Agaram | 2022-06-10 | 2 | -4/+6 |
| | | |||||
| * | remove some memory leaks from rendered fragments | Kartik K. Agaram | 2022-06-10 | 5 | -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 concatenations | Kartik K. Agaram | 2022-06-10 | 1 | -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 test | Kartik K. Agaram | 2022-06-09 | 1 | -0/+17 |
| | | |||||
| * | bugfix: cut (C-x) without first selecting anything | Kartik K. Agaram | 2022-06-09 | 2 | -0/+5 |
| | | |||||
| * | fix a corner case when selecting text | Kartik K. Agaram | 2022-06-09 | 2 | -9/+51 |
| | | | | | | The hard part here is keeping click-drag selection working (without pressing and holding shift). | ||||
| * | move | Kartik K. Agaram | 2022-06-09 | 1 | -4/+4 |
| | | |||||
| * | . | Kartik K. Agaram | 2022-06-09 | 1 | -4/+2 |
| | | |||||
| * | test both ways of selecting text with mouse | Kartik K. Agaram | 2022-06-09 | 1 | -4/+25 |
| | | |||||
| * | experiment: blinking cursor | Kartik K. Agaram | 2022-06-09 | 2 | -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 text | Kartik K. Agaram | 2022-06-09 | 1 | -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 thicker | Kartik K. Agaram | 2022-06-09 | 1 | -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 cursor | Kartik K. Agaram | 2022-06-09 | 1 | -1/+1 |
| | | |||||
| * | fix contact link | Kartik K. Agaram | 2022-06-09 | 1 | -1/+1 |
| | | |||||
| * | experiment: turn off JIT | Kartik K. Agaram | 2022-06-09 | 1 | -0/+5 |
| | | | | | This seems to speed up copy! What does it slow down? | ||||
| * | move | Kartik K. Agaram | 2022-06-09 | 1 | -6/+6 |
| | | |||||
| * | speeding up copy, attempt 1 | Kartik K. Agaram | 2022-06-09 | 1 | -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 handling | Kartik K. Agaram | 2022-06-07 | 2 | -2/+27 |
| | | | | | Thanks John Blommers for the report! | ||||
| * | forgot to commit documentation for the commandline arg | Kartik K. Agaram | 2022-06-07 | 1 | -0/+10 |
| | | |||||
| * | first commandline arg: window dimensions | Kartik K. Agaram | 2022-06-07 | 1 | -8/+33 |
| | | | | | Hopefully there won't be too many others. | ||||
| * | use app name in window title | Kartik K. Agaram | 2022-06-07 | 1 | -1/+1 |
| | | |||||
| * | clearer discription of how to run lines.love | Kartik K. Agaram | 2022-06-07 | 1 | -5/+22 |
| | | |||||
| * | a likely source of issues | Kartik K. Agaram | 2022-06-07 | 1 | -0/+4 |
| | | |||||
| * | warn on unused commandline args | Kartik K. Agaram | 2022-06-07 | 1 | -0/+4 |
| | | |||||
| * | obsolete comment | Kartik K. Agaram | 2022-06-07 | 1 | -1/+0 |
| | | |||||
| * | extract a function | Kartik K. Agaram | 2022-06-07 | 1 | -11/+14 |
| | | |||||
| * | allow the window to be resized | Kartik K. Agaram | 2022-06-07 | 1 | -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 typo | Kartik K. Agaram | 2022-06-07 | 1 | -1/+1 |
| | | |||||
| * | fix a crash | Kartik K. Agaram | 2022-06-06 | 1 | -1/+3 |
| | | | | | | This one isn't worth debugging. We know how to recreate this data on demand. | ||||
| * | flesh out Readme | Kartik K. Agaram | 2022-06-06 | 1 | -0/+49 |
| | | |||||
| * | another known issue | Kartik K. Agaram | 2022-06-06 | 1 | -4/+4 |
| | | |||||
| * | autosave on cut/paste | Kartik K. Agaram | 2022-06-05 | 1 | -0/+2 |
| | | |||||
| * | additional logging for an active bug | Kartik K. Agaram | 2022-06-05 | 1 | -1/+5 |
| | | |||||
| * | . | Kartik K. Agaram | 2022-06-05 | 1 | -1/+1 |
| | | |||||
| * | record another known issue I don't know how to fix yet | Kartik K. Agaram | 2022-06-05 | 1 | -0/+5 |
| | | | | | | | | Perhaps I need to switch to the next more sophisticated data structure for Lines: a gap buffer around the line the cursor is on. I'm not sure why it would help here, though. | ||||
| * | another bugfix in scrolling while inserting text | Kartik K. Agaram | 2022-06-05 | 3 | -4/+23 |
| | | | | | | | I'm being unprincipled at the moment between pos and x,y coordinates. Whatever is more convenient. Perhaps a cleaner approach will come to me over time. | ||||
| * | bugfix in previous commit | Kartik K. Agaram | 2022-06-05 | 2 | -0/+13 |
| | | | | | | | | | I almost pushed this to production. That would have been catastrophic; the very first keystroke anyone typed into the editor would have failed. And in the process, this fixes the next bug on my TODO list! Paste on first line wasn't working. Now it is. | ||||
| * | check for scroll when just typing | Kartik K. Agaram | 2022-06-05 | 2 | -2/+38 |
| | | |||||
| * | rename | Kartik K. Agaram | 2022-06-05 | 2 | -7/+7 |
| | | |||||
| * | some unnecessary mutations | Kartik K. Agaram | 2022-06-05 | 2 | -8/+0 |
| | | | | | | Why are we not modifying Screen_top1.pos in these places? Because we don't really need to modify Screen_top1 at all. | ||||
| * | some typos | Kartik K. Agaram | 2022-06-05 | 2 | -5/+5 |
| | | |||||
| * | bugfix: backspace from start of file | Kartik K. Agaram | 2022-06-04 | 1 | -4/+1 |
| | | |||||
| * | make online help fit within a drawing | Kartik K. Agaram | 2022-06-04 | 1 | -9/+3 |
| | | |||||
| * | yet another key conflict | Kartik K. Agaram | 2022-06-04 | 2 | -3/+3 |
| | | |||||
| * | regression: couldn't do many drawing operations because line.y was reset | Kartik K. Agaram | 2022-06-04 | 2 | -1/+8 |
| | | |||||
| * | switch circles to 'o' to avoid conflicting with copy | Kartik K. Agaram | 2022-06-04 | 2 | -4/+4 |
| | | |||||
| * | bugfix in help | Kartik K. Agaram | 2022-06-04 | 1 | -2/+2 |
| | | |||||
| * | try to maintain a reasonable line width | Kartik K. Agaram | 2022-06-04 | 2 | -16/+16 |
| | | |||||