Delete key

[Jean-Pierre A. Radley]

Mark Luljak propounded (on Thu, Mar 20, 2014 at 05:01:55PM -0400):
| On Thu, Mar 20, 2014 at 04:49:50PM -0400, Kenneth Brody thus spoke:
| > On 3/20/2014 3:54 PM, William J. McEachran wrote:
| > > I just don't think that hitting the DEL key should behave so unexpectedly
| > > ... inserting "~3"'s in fields.
| > 
| > What would you expect a program to do when a sequence of characters comes 
| > in, which is not defined to be any particular "keystroke"?  Numerous defined 
| > keystrokes start with "ESC [", but none are then followed by a "3".  What 
| > would be your "expected behavior" when "ESC [ 3 ~" is sent to filePro? 
| > (Remember, filePro has no way of knowing that a single keystroke generated 
| > those characters, up to and including the tilde.)
| 
| Don't ask questions to which you don't actually want the answer.
| 
| Realistically?  You do exactly what mutt does, and you look at a timer on
| the input.  If the next character follows close enough to the first escape,
| it's part of the key's sequence; if there is a long enough delay, the next
| character is treated as separate.
| 
| This is why things like Escape-V for expand/collapse all threads (which may
| actually be a personal macro, not a default) require me to wait a slight
| pause before the V, rather than hit them in quick succession.

Esc-v and ESC-V are default macros in mutt.

| You're litereally looking at it at the nanosecond level in high-resolution
| time.  It's a fairly safe bet that if two characters are separated by an
| extremely small number of nanoseconds, they're related.  In practise, that
| timer has been set a bit too high in mutt, as I can trigger it fairly
| easily.  If it's settable, no problem.  I've just gotten in the habit of
| not hitting the two very close together because I know how it behaves.
| Actually, it doesn't look like it's tunable in mutt...or I'm looking for
| the wrong keywords in the manual.

I've perused mutt source code and don't see where any time-sensitive
parsing of keyboard input is occurring.

-- 
JP