Thu 20 Mar 2008 07:16:38 PM UTC, comment #2:
Oh, of course, this is how some sequences get generated, for example the higher F-key sequences are actually sent as Alt-[-something. Nano really cant do anything about that afaik, so leaving Meta-] the shortcut makes the most sense. In fact it makes sense for nano to print an error if the user attempts to map Meta-[.
|
Thu 20 Mar 2008 09:09:11 AM UTC, comment #1:
OK, I have noticed this isn't a Nano issue at all - it was the change to 'Alt-[' that made it become apparent.
I have found that on my system, at the console or in a term, if I type 'Atl-[' I get a good one second delay before the system bell rings an error. All other combinations are instant. It seems to produce two chars somehow, the first does something, and the then the second it really 'Alt-['.
Strange.
Nick
|
Thu 20 Mar 2008 07:21:41 AM UTC, original submission:
I noticed that the key change to 'match brackets' - 'Alt-[' operated on my system extremely slowly - about 1 second to locate and jump to matching bracket, even if the document only contained this:
{ }
Chris has reverted the key back to the way it was - 'Alt-]', and now it works instantly as before.
But as an aside to this, if I now key in 'Alt-[', I still get a good second delay until the 'Unknown Command' pops up - any other unknown commands issue this warning instantly (I just noticed this happens on my old build of nano-2.0.99-cvs too)
Some info:
GNU nano version 2.1.0-svn (compiled 06:48:13, Mar 20 2008)
(C) 1999, 2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007
Free Software Foundation, Inc.
Email: -unavailable- Web: http://www.nano-editor.org/
Compiled options: --disable-mouse --disable-nls --enable-nanorc --enable-utf8
Athlon 1.2Ghz, 1.5GB ram... Slackware, Fluxbox WM. I use mrxvt term.
Nick
|