marek jedlinski <[EMAIL PROTECTED]> wrote:
>
> However, I think that the first, simpler suggestion would be
> relatively easy to implement. It just needs an additional .rc
> setting, an if clause somewhere in the code, and a key binding for
> 'mark-read'.
All things are simple to he who doesn't have to do the work. :)
> > You can't type such a key sequence. :)
>
> That's weird: you're saying Linux can't do something DOS can? :)
Linux is following the VT100 terminal behavior that came before it was
invented. :)
Linux's console is capable of a raw mode where the exact keys that are
depressed can be passed to an application. Mutt does not even attempt
to do this, as it is a Unix program, designed to be portable across
multiple platforms. As such, it uses the standard tty interfaces that
all Unix systems provide. And I don't know of any Unix console driver
that returns different keystrokes for control-arrow keys vs normal arrow
keys.
> Are you saying that the inability to recognize Ctrl-arrow is only
> specific to the xterm, or to all terminals, inclusing the 'linux'
> console?
You can test this out by typing Ctrl-V at your shell prompt, then
pressing the Up-Arrow key. You should see "^[[A" on your input line;
that's the sequence of VT100 codes for cursor-up. Then, if you type
Ctrl-V, followed by Ctrl-Up-Arrow, you'll see that the exact same key
sequence is generated.
If you really want to, I bet you could hack your console keyboard map to
generate a different key sequence for Ctrl-Arrows. Then you just teach
Mutt about those new sequences, and away you go. :)
--
David DeSimone | "The doctrine of human equality reposes on this:
[EMAIL PROTECTED] | that there is no man really clever who has not
Hewlett-Packard | found that he is stupid." -- Gilbert K. Chesterson
Convex Division | PGP: 5B 47 34 9F 3B 9A B0 0D AB A6 15 F1 BB BE 8C 44
