Marcel Kilgus writes: > > I already use this keystroke in a number of my programs for the purpose (F5 > > in Qwirc, FF and others, and F10 in older programs) so in my case Id want to > > override, disable or avoid this facility in individual programs. > > Why? It wouldn't change the behaviour of your program at all. It would > just add the additional feature of reacting to F10 within a read-line > trap (instead of doing nothing at all).
Just trying to be controversial in these quiete times ;) There are however some good reasons. A number of my programs (and probably other people's too) have their own line editor using editing keystrokes that are not understood by the edlin trap. In FF and Qwirc, for example, I use F5 to stuff the resulting string into the global stuffer buffer and F10 to stuff it into a local buffer. This is so you have a CHOICE: A frequently used file name might be held in the global stuffer buffer while intermediate or more dynamic data can be held in the local buffer. In some older programs I use a different scheme, with F10 stuffing the edited string into the stuffer buffer. Those, and any other existing programs that do something similar, will find that they get two copies of the keyboard queue contents. The first copy would hold what iob.edlin thinks is the resultant string (accessed by Alt+Shift+Space or equivalent) while the second would hold what your program knows to be the correct version. Disconcerting, messy and quite unnecessary, methinks. Per
