I just updated my delimitMate (yeah it's been a while), and the new behavior introduced by the "fix" for #95 is terrible. It assumes that I always keep all my delimiters balanced at all times, and therefore trying to type a close-delimiter should always try to jump if possible. But writing code is not ideal, and my delimiters aren't always balanced. If I have psueod-code like
loop {
doSomething();
another_loop {
code
more code
even more code here
|
}
(where | is the cursor), then pressing } jumps past the final } instead of inserting the much-needed close-brace.
The only time I ever expect a delimiter to be jumped-past is when my cursor is already at the delimiter. Any other time, it should just insert the delimiter that I requested.
lilyball
commented
11 years ago
I just updated my delimitMate (yeah it's been a while), and the new behavior introduced by the "fix" for #95 is terrible. It assumes that I always keep all my delimiters balanced at all times, and therefore trying to type a close-delimiter should always try to jump if possible. But writing code is not ideal, and my delimiters aren't always balanced. If I have psueod-code like
(where
|is the cursor), then pressing}jumps past the final}instead of inserting the much-needed close-brace.The only time I ever expect a delimiter to be jumped-past is when my cursor is already at the delimiter. Any other time, it should just insert the delimiter that I requested.