about summary refs log tree commit diff stats
Commit message (Collapse)AuthorAgeFilesLines
...
* 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.
* one more known issueKartik K. Agaram2022-06-031-0/+3
|
* more precise search highlightingKartik K. Agaram2022-06-032-6/+5
|
* extract a functionKartik K. Agaram2022-06-032-20/+25
|
* extract a couple of filesKartik K. Agaram2022-06-034-1193/+1202
|
* bugfix: restore state after C-f (find)Kartik K. Agaram2022-06-032-8/+14
|
* taking stockKartik K. Agaram2022-06-031-0/+4
| | | | | | | | couple of more temporary bugs: find sometimes draws highlighted text in wrong place esc after C-f sometimes ends up with cursor before screen top But the known issues are harder.
* highlight selection while draggingKartik K. Agaram2022-06-032-17/+47
| | | | | | | 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 dragKartik K. Agaram2022-06-033-12/+27
| | | | Doesn't yet highlight while dragging.
* renameKartik K. Agaram2022-06-032-12/+12
|
* local varKartik K. Agaram2022-06-031-60/+61
|
* up arrow to search previousKartik K. Agaram2022-06-032-0/+52
|
* switch freehand hotkey to eliminate conflict with searchKartik K. Agaram2022-06-022-2/+2
| | | | I'm now following Inkscape, and the mnemonic is 'pencil'.
* switch copy/paste to ctrl- hotkeysKartik K. Agaram2022-06-022-48/+49
|
* switch undo/redo to ctrl- hotkeysKartik K. Agaram2022-06-022-22/+20
|
* default font size and line-heightKartik K. Agaram2022-06-021-4/+10
|
* extract a new variableKartik K. Agaram2022-06-022-94/+63
|
* crisp font renderingKartik K. Agaram2022-06-025-283/+228
|
* find textKartik K. Agaram2022-06-022-9/+119
|
* scroll if necessary on pasteKartik K. Agaram2022-06-021-0/+23
|
* renameKartik K. Agaram2022-06-021-2/+2
|
generated by cgit-pink 1.4.1-2-gfad0 (git 2.36.2.497.gbbea4dcf42) at 2024-07-07 19:06:42 +0000