| Commit message (Collapse) | Author | Age | Files | Lines | ||
|---|---|---|---|---|---|---|
| ... | ||||||
| * | stop handling nil screen_line_starting_pos everywhere | Kartik K. Agaram | 2022-06-10 | 1 | -1/+0 | |
| | | | | | Things seem to be working.. | |||||
| * | more precise scroll on paste | Kartik K. Agaram | 2022-06-10 | 1 | -19/+4 | |
| | | ||||||
| * | faster paste | Kartik K. Agaram | 2022-06-10 | 1 | -9/+7 | |
| | | | | | | We don't need to perform the scroll calculations after inserting every single character from the clipboard. | |||||
| * | revert previous commit | Kartik K. Agaram | 2022-06-10 | 1 | -5/+15 | |
| | | ||||||
| * | experiment: extremely precise scrolling on paste | Kartik K. Agaram | 2022-06-10 | 1 | -15/+5 | |
| | | | | | But this is too slow. | |||||
| * | while we're at it, undo naming points | Kartik K. Agaram | 2022-06-10 | 1 | -0/+2 | |
| | | ||||||
| * | stop saving the entire file when modifying drawings | Kartik K. Agaram | 2022-06-10 | 1 | -0/+8 | |
| | | | | | Now we just disallow that entirely. | |||||
| * | undo creating new drawings | Kartik K. Agaram | 2022-06-10 | 1 | -1/+3 | |
| | | ||||||
| * | extract scrolling logic out of insert_at_cursor | Kartik K. Agaram | 2022-06-10 | 1 | -0/+6 | |
| | | ||||||
| * | extract scrolling logic out of insert_return | Kartik K. Agaram | 2022-06-10 | 1 | -0/+3 | |
| | | ||||||
| * | remove some memory leaks from rendered fragments | Kartik K. Agaram | 2022-06-10 | 1 | -0/+3 | |
| | | | | | | | | | | | | | | | | 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. | |||||
| * | fix a corner case when selecting text | Kartik K. Agaram | 2022-06-09 | 1 | -9/+21 | |
| | | | | | | The hard part here is keeping click-drag selection working (without pressing and holding shift). | |||||
| * | . | Kartik K. Agaram | 2022-06-09 | 1 | -4/+2 | |
| | | ||||||
| * | experiment: blinking cursor | Kartik K. Agaram | 2022-06-09 | 1 | -0/+4 | |
| | | | | | | | | | | 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. | |||||
| * | experiment: turn off JIT | Kartik K. Agaram | 2022-06-09 | 1 | -0/+5 | |
| | | | | | This seems to speed up copy! What does it slow down? | |||||
| * | more defensive resize handling | Kartik K. Agaram | 2022-06-07 | 1 | -2/+23 | |
| | | | | | Thanks John Blommers for the report! | |||||
| * | 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 | |
| | | ||||||
| * | 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. | |||||
| * | autosave on cut/paste | Kartik K. Agaram | 2022-06-05 | 1 | -0/+2 | |
| | | ||||||
| * | . | Kartik K. Agaram | 2022-06-05 | 1 | -1/+1 | |
| | | ||||||
| * | another bugfix in scrolling while inserting text | Kartik K. Agaram | 2022-06-05 | 1 | -0/+1 | |
| | | | | | | | 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. | |||||
| * | rename | Kartik K. Agaram | 2022-06-05 | 1 | -2/+2 | |
| | | ||||||
| * | some unnecessary mutations | Kartik K. Agaram | 2022-06-05 | 1 | -4/+0 | |
| | | | | | | Why are we not modifying Screen_top1.pos in these places? Because we don't really need to modify Screen_top1 at all. | |||||
| * | regression: couldn't do many drawing operations because line.y was reset | Kartik K. Agaram | 2022-06-04 | 1 | -1/+7 | |
| | | ||||||
| * | try to maintain a reasonable line width | Kartik K. Agaram | 2022-06-04 | 1 | -15/+15 | |
| | | ||||||
| * | . | Kartik K. Agaram | 2022-06-04 | 1 | -4/+0 | |
| | | ||||||
| * | select text with shift + mouseclick | Kartik K. Agaram | 2022-06-04 | 1 | -2/+8 | |
| | | | | | | | | It's still a bit simple-minded. Most software will keep the first bound fixed and move the second. Lines currently has the bounds in a queue of sorts. But I have a test to indicate the behavior that is definitely desired. We'll see if we need it to get more complex. | |||||
| * | bugfix: restore state after C-f (find) | Kartik K. Agaram | 2022-06-03 | 1 | -4/+6 | |
| | | ||||||
| * | highlight selection while dragging | Kartik K. Agaram | 2022-06-03 | 1 | -5/+7 | |
| | | | | | | | | Mouse stuff is pretty strenuous. For the first time I have to be careful not to recompute too often. And I ran into a race condition for the first time where resetting line.y within App.draw meant mouse clicks were extremely unlikely to see line.y set. | |||||
| * | select text using mouse drag | Kartik K. Agaram | 2022-06-03 | 1 | -10/+15 | |
| | | | | | Doesn't yet highlight while dragging. | |||||
| * | rename | Kartik K. Agaram | 2022-06-03 | 1 | -2/+2 | |
| | | ||||||
| * | up arrow to search previous | Kartik K. Agaram | 2022-06-03 | 1 | -0/+2 | |
| | | ||||||
| * | switch copy/paste to ctrl- hotkeys | Kartik K. Agaram | 2022-06-02 | 1 | -0/+48 | |
| | | ||||||
| * | switch undo/redo to ctrl- hotkeys | Kartik K. Agaram | 2022-06-02 | 1 | -0/+18 | |
| | | ||||||
| * | default font size and line-height | Kartik K. Agaram | 2022-06-02 | 1 | -4/+10 | |
| | | ||||||
| * | extract a new variable | Kartik K. Agaram | 2022-06-02 | 1 | -1/+2 | |
| | | ||||||
| * | crisp font rendering | Kartik K. Agaram | 2022-06-02 | 1 | -4/+20 | |
| | | ||||||
| * | find text | Kartik K. Agaram | 2022-06-02 | 1 | -5/+43 | |
| | | ||||||
| * | . | Kartik K. Agaram | 2022-06-02 | 1 | -1/+1 | |
| | | ||||||
| * | rename | Kartik K. Agaram | 2022-06-02 | 1 | -1/+1 | |
| | | ||||||
| * | bugfix: undo drawing creation | Kartik K. Agaram | 2022-06-02 | 1 | -0/+1 | |
| | | | | | | Also clean up drawing state to make sure we don't get into hard-to-debug situations. | |||||
| * | after much struggle, a brute-force undo | Kartik K. Agaram | 2022-06-02 | 1 | -0/+5 | |
| | | | | | | | | | | Incredibly inefficient, but I don't yet know how to efficiently encode undo mutations that can span multiple lines. There seems to be one bug related to creating new drawings; they're not spawning events and undoing past drawing creation has some weird artifacts. Redo seems to consistently work, though. | |||||
| * | . | Kartik K. Agaram | 2022-05-29 | 1 | -6/+0 | |
| | | ||||||
| * | selecting text and deleting selections | Kartik K. Agaram | 2022-05-29 | 1 | -0/+11 | |
| | | | | | | | I've written a few tests for delete_selection, but the way different operations initialize the selection seems fairly standard and not worth testing so far. | |||||
| * | update some documentation | Kartik K. Agaram | 2022-05-29 | 1 | -3/+6 | |
| | | ||||||
| * | move some code | Kartik K. Agaram | 2022-05-28 | 1 | -28/+0 | |
| | | | | | | I had this idea originally to keep text.lua oblivious to drawings. But that hasn't been true for some time. Losing battle. | |||||