about summary refs log tree commit diff stats
path: root/edit.mu
Commit message (Collapse)AuthorAgeFilesLines
* 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 '+'?
* 2133Kartik K. Agaram2015-09-021-0/+4
|
* 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.
* 2123 - bugfix in wrapping current lineKartik K. Agaram2015-09-011-1/+33
|
* 2122 - undo/redo should now be workingKartik K. Agaram2015-09-011-22/+219
|
* 2121 - undo now supports the 'delete' keyKartik K. Agaram2015-09-011-12/+199
| | | | 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-311-7/+126
|
* 2117Kartik K. Agaram2015-08-311-8/+0
|
* 2116Kartik K. Agaram2015-08-311-16/+16
|
* 2115Kartik K. Agaram2015-08-301-3/+3
| | | | | 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
|
* 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-291-2/+2
|
* 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-291-275/+179
| | | | 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-281-49/+34
| | | | | | | | | | | | 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
|
* 2089 - undo support for mouse clicksKartik K. Agaram2015-08-281-2/+75
|
* 2088 - warn on duplicate scenario nameKartik K. Agaram2015-08-281-1/+1
|
* 2087Kartik K. Agaram2015-08-281-1/+4
|
* 2086 - reset cursor on resizeKartik K. Agaram2015-08-281-13/+11
| | | | Also drop some redundancy with 'render-all'.
* 2085 - undo/redo now working for simple typingKartik K. Agaram2015-08-271-0/+50
| | | | | Not yet useable, because we never ever stop coalescing operations. That will happen when we introduce a second type of operation.
* 2084Kartik K. Agaram2015-08-271-23/+155
|
* 2083Kartik K. Agaram2015-08-261-2/+42
|
* 2082Kartik K. Agaram2015-08-261-1/+92
|
* 2081 - preliminary data model for undoKartik K. Agaram2015-08-261-4/+44
|
* 2079Kartik K. Agaram2015-08-261-12/+7
| | | | Cleanup 2078.
* 2078 - update entire screen on tb_present()Kartik K. Agaram2015-08-261-1/+11
| | | | | | | | | | | | | | | | | | | Termbox had been taking shortcuts when it thinks the screen hasn't changed, which doesn't work if some other process messes up the screen. The Go version has a Sync method in addition to Flush/tb_present for precisely this eventuality. But it feels like an unnecessary optimization given C's general speed. Just drop it altogether. --- This took me a long time to track down, and interestingly I found myself writing a new tracing primitive before I remembered how to selectively trace just certain layers during manual tests. I'm scared of generating traces not because of performance but because of the visual noise. Be aware of this. I'm going to clean up $log now. Maybe I should also stop using $print..
* 2077Kartik K. Agaram2015-08-251-1/+1
|
generated by cgit-pink 1.4.1-2-gfad0 (git 2.36.2.497.gbbea4dcf42) at 2024-07-02 11:05:05 +0000