diff options
author | Kartik K. Agaram <vc@akkartik.com> | 2015-07-01 13:28:09 -0700 |
---|---|---|
committer | Kartik K. Agaram <vc@akkartik.com> | 2015-07-01 13:32:07 -0700 |
commit | 61a42dc1c23f02e889eb6116d5a602dcefde7b24 (patch) | |
tree | 2a6565fdd4f1dc7f610574d9ab07716e472a73de /factorial.mu | |
parent | 8529e532499027ac37318b001700fe5a9629d2e8 (diff) | |
download | mu-61a42dc1c23f02e889eb6116d5a602dcefde7b24.tar.gz |
1694
I started fixing scenario editor-inserts-character-at-wrapped-cursor, but as I work further I notice there's an irreconcilable ambiguity in the approach of letting the cursor wrap in a non-wrapped line: if a cursor is at column 0 and the previous line occupies the entire width, should the next character you insert go before (assuming a wrapped cursor) or after the newline (assuming you're at the start of the next line)? No way to distinguish the two cases. One approach would be to delete the newline and have the cursor replace it with whatever you type. Then you have to hit a newline again to separate. But the simpler way is to simply wrap the moment the line grows to width-1, always leaving room for the cursor. Yeah, let's switch to that approach.
Diffstat (limited to 'factorial.mu')
0 files changed, 0 insertions, 0 deletions