about summary refs log tree commit diff stats
path: root/073scenario_screen_test.mu
diff options
context:
space:
mode:
authorKartik K. Agaram <vc@akkartik.com>2015-07-01 13:28:09 -0700
committerKartik K. Agaram <vc@akkartik.com>2015-07-01 13:32:07 -0700
commit61a42dc1c23f02e889eb6116d5a602dcefde7b24 (patch)
tree2a6565fdd4f1dc7f610574d9ab07716e472a73de /073scenario_screen_test.mu
parent8529e532499027ac37318b001700fe5a9629d2e8 (diff)
downloadmu-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 '073scenario_screen_test.mu')
0 files changed, 0 insertions, 0 deletions