about summary refs log tree commit diff stats
Commit message (Collapse)AuthorAgeFilesLines
...
* 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
|
* .Kartik K. Agaram2022-06-051-1/+1
|
* record another known issue I don't know how to fix yetKartik K. Agaram2022-06-051-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 textKartik K. Agaram2022-06-053-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 commitKartik K. Agaram2022-06-052-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 typingKartik K. Agaram2022-06-052-2/+38
|
* renameKartik K. Agaram2022-06-052-7/+7
|
* some unnecessary mutationsKartik K. Agaram2022-06-052-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 typosKartik K. Agaram2022-06-052-5/+5
|
* bugfix: backspace from start of fileKartik K. Agaram2022-06-041-4/+1
|
* make online help fit within a drawingKartik K. Agaram2022-06-041-9/+3
|
* yet another key conflictKartik K. Agaram2022-06-042-3/+3
|
* regression: couldn't do many drawing operations because line.y was resetKartik K. Agaram2022-06-042-1/+8
|
* switch circles to 'o' to avoid conflicting with copyKartik K. Agaram2022-06-042-4/+4
|
* bugfix in helpKartik K. Agaram2022-06-041-2/+2
|
* try to maintain a reasonable line widthKartik K. Agaram2022-06-042-16/+16
|
* .Kartik K. Agaram2022-06-041-4/+0
|
* experiment: slightly adaptive scrollingKartik K. Agaram2022-06-042-16/+56
| | | | | | | | | | | When long wrapping lines go past the current page, I find myself scrolling before I get to the bottom. So let's scroll less, usually from the start of the bottom-most line, even if it wraps multiple screen lines. The challenge with this is to ensure that a long line that fills the whole page by itself doesn't get you stuck. I take some care to make sure <pagedown> always makes forward progress.
* select text with shift + mouseclickKartik K. Agaram2022-06-044-7/+57
| | | | | | | 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.
* make cursor more obviousKartik K. Agaram2022-06-041-1/+1
| | | | | Let's see if this is good enough. I can also bump up to 4px radius if I need to.
generated by cgit-pink 1.4.1-2-gfad0 (git 2.36.2.497.gbbea4dcf42) at 2024-12-17 14:20:06 +0000