about summary refs log tree commit diff stats
Commit message (Collapse)AuthorAgeFilesLines
* 2140 - refresh screen after falling behindKartik K. Agaram2015-09-042-11/+62
| | | | | This bit of code is complex enough now that I'm bothered I can't write tests for has-more-events?
* 2139Kartik K. Agaram2015-09-041-0/+1
|
* 2138 - warn on jump to an ambiguous labelKartik K. Agaram2015-09-042-44/+224
| | | | | | | | | | | | | | | | | | | | This seemingly simple goal uncovered a little nest of bugs: it turns out I've been awash in ambiguous labels until now. My baseline recipes in edit.mu were clean, but they introduced duplicate <waypoints> -- and *those* waypoints contained +jump-targets. Result: duplicate jump targets, so that I wasn't jumping where I thought I was jumping. Somehow I happened to be picking one of the alternatives that magically kept these issues quiescent. My first plan to fix this was to mangle names of all labels inside before/after fragments, keep the jump targets private to their fragment. But the labels also include more waypoints! Mangle those, and I can't tangle to them anymore. Solution: harden the convention that jump targets begin with '+' and waypoints are surrounded by '<>'. Mangle jump targets occurring inside before/after fragments to keep them private to their lexical fragment, but *don't* mangle waypoints, which must remain globally accessible.
* 2137Kartik K. Agaram2015-09-038-10/+0
|
* 2136 - distinguish <tangle-points> from +labelsKartik K. Agaram2015-09-031-124/+124
| | | | Tangle points aren't unique within a recipe and cannot be jumped to.
* 2135 - bugfix: couldn't see warnings sometimesKartik K. Agaram2015-09-031-16/+49
| | | | | | I'm starting to feel the need for separating labels to jump to (so must be unique per recipe) from labels you can tangle at (need not be unique). Maybe just use a sigil different from '+'?
* 2134 - bugfix: comment terminated by eofKartik K. Agaram2015-09-021-5/+17
| | | | | I ran into this inside 'reload' when I left a trailing comment at the end of the editor.
* 2133Kartik K. Agaram2015-09-021-0/+4
|
* 2132 - support for ctrl + arrow keysKartik K. Agaram2015-09-023-5/+29
|
* 2131 - better tb_sync()Kartik K. Agaram2015-09-021-6/+10
| | | | | | | | | For some reason porting the termbox-go implementation was still leaving some gunk from git on screen when I ran my usual test: $ mkdir lesson; cd lesson; git init; mu edit.mu Then hit F4, generating messages from git on the initial commit. Then hit ctrl-l to clear all git gunk.
* 2130Kartik K. Agaram2015-09-021-10/+7
|
* 2129 - bugfix: clicking on 'menu' barKartik K. Agaram2015-09-021-3/+24
|
* 2128Kartik K. Agaram2015-09-011-0/+20
|
* 2127 - colorize sandboxesKartik K. Agaram2015-09-011-1/+70
| | | | | | This is really testing our premise that mu is robust to duplication. The new routine diverges from the old in only 1 out of 68 lines.. and also has no tests.
* 2126Kartik K. Agaram2015-09-012-2/+2
|
* 2125 - bugfix for containers in the environmentKartik K. Agaram2015-09-011-0/+5
| | | | | We don't want to add duplicate fields to the container everytime we hit F4.
* 2124Kartik K. Agaram2015-09-011-4/+7
| | | | Make a test more robust, especially when running just until layer 38.
* 2123 - bugfix in wrapping current lineKartik K. Agaram2015-09-011-1/+33
|
* 2122 - undo/redo should now be workingKartik K. Agaram2015-09-012-22/+244
|
* 2121 - undo now supports the 'delete' keyKartik K. Agaram2015-09-012-12/+278
| | | | Still to go: ctrl-k and ctrl-u.
* 2120Kartik K. Agaram2015-09-011-26/+40
|
* 2119Kartik K. Agaram2015-08-311-20/+53
|
* 2118 - start on undo deletionsKartik K. Agaram2015-08-312-7/+139
|
* 2117Kartik K. Agaram2015-08-311-8/+0
|
* 2116Kartik K. Agaram2015-08-311-16/+16
|
* 2115Kartik K. Agaram2015-08-302-3/+39
| | | | | Merging in unnecessary '0/empty' fields was a pain, and also made me do some additional debugging in the last commit.
* 2114 - back to undo: coalesce move operationsKartik K. Agaram2015-08-301-6/+92
|
* 2113 - stop updating entire screen on tb_present()Kartik K. Agaram2015-08-294-0/+32
| | | | | | | | | | | | | | | | | | | | Mu still isn't so optimized that I can be profligate with spare cycles. Instead we'll follow termbox-go's example and create a new API routine called tb_sync() (after discussion with termbox's author). Now we only need use tb_sync() on ctrl-l. For everything else use the optimized render. Now I think I've eradicated all signs of "cursor thrashing" during refresh, in spite of how slow mu is as an interpreted language. We only render the whole screen in some situations, and only if there's no more input, and even then we only refresh the parts of the screen that changed. Thanks Jack and Caleb Couch for providing the impetus behind commits 2109-2113. I've been lazy about writing tests for all this, but it's still good to know I could, if I wanted to.
* 2112 - avoid repaint when page-up/down hit edge of textKartik K. Agaram2015-08-291-0/+17
|
* 2111 - avoid repaint when up/down hit edge of textKartik K. Agaram2015-08-291-5/+16
|
* 2109 - avoid unnecessary repaintsKartik K. Agaram2015-08-291-0/+6
| | | | | | | | | We're still seeing mu hang for long periods if people press and hold say an arrow key, as the events are all processed. Hopefully this will stop that from taking too long. But the real problem is still printing junk to screen because of sluggishness in processing input.
* 2108 - undo touch events *outside tests*Kartik K. Agaram2015-08-291-2/+159
| | | | Test-only routines like 'editor-event-loop' are a pox.
* 2107Kartik K. Agaram2015-08-291-22/+171
|
* 2106 - undo enter, but don't coalesce with surrounding typingKartik K. Agaram2015-08-291-27/+132
|
* 2105Kartik K. Agaram2015-08-292-3/+3
|
* 2104Kartik K. Agaram2015-08-291-2/+3
|
* 2103Kartik K. Agaram2015-08-291-14/+14
|
* 2102Kartik K. Agaram2015-08-291-0/+4
|
* 2101 - teach 'assume-console' about names of keysKartik K. Agaram2015-08-292-280/+255
| | | | I'm sick of using the 'replace-in-console' hack.
* 2100 - starting to flesh out coalescing of undo operationsKartik K. Agaram2015-08-291-2/+17
|
* 2099 - undo support for moving to start/end of lineKartik K. Agaram2015-08-291-0/+200
|
* 2098 - undo support for page-up/downKartik K. Agaram2015-08-291-0/+164
|
* 2097 - undo support for arrow keysKartik K. Agaram2015-08-291-78/+246
|
* 2096 - clear redo when adding to undoKartik K. Agaram2015-08-291-3/+59
| | | | One drawback of my approach: if you move the cursor you lose your redo.
* 2095Kartik K. Agaram2015-08-2831-222/+64
| | | | | | | | | | | | Finally terminate the experiment of keeping debug prints around. I'm also going to give up on maintaining counts. What we really need is two kinds of tracing: a) For tests, just the domain-specific facts, organized by labels. b) For debugging, just transient dumps to stdout. b) only works if stdout is clean by default. Hmm, I think this means 'stash' should be the transient kind of trace.
* 2094Kartik K. Agaram2015-08-281-45/+126
|
* 2093Kartik K. Agaram2015-08-281-6/+6
|
* 2092Kartik K. Agaram2015-08-281-5/+5
|
* 2091Kartik K. Agaram2015-08-281-30/+30
|
* 2090Kartik K. Agaram2015-08-281-0/+61
|
generated by cgit-pink 1.4.1-2-gfad0 (git 2.36.2.497.gbbea4dcf42) at 2024-11-23 16:22:55 +0000