bug#5696: 23.1; emacsclient misinterprets (?) keys on first use

bug#5696: 23.1; emacsclient misinterprets (?) keys on first use

[Paul Madden]

I start the emacs daemon as "emacs -Q --daemon" and then run "emacsclient -t 
file". The four cursor-movement keys, as well as page-up and page-down, seem to 
be misinterpreted if one of them is the first key pressed in emacsclient. For 
example, page-down inserts the text "6~" in the buffer if it is the first key 
pressed in emacsclient after the emacs daemon is started. The down arrow key 
causes the following message to appear in the minibuffer: "Font-lock mode will 
override any faces you set in this buffer". Right arrow says: "M-o C is undefined".

But if any of these keys is pressed a second time, it performs its expected
function (scroll-up, next-line, forward-char, respectively). Also, if a second
emacsclient is started, these keys function correctly at all times. But if
I kill and start a new emacs server, the first use of any of these keys again
appears to be misinterpreted.

If I kill the emacs server and then run a standalone emacs (e.g. emacs -nw file)
the keys work correctly at all times. They also work correctly at all times if
I use "emacsclient -c" instead of "-t".

I am using GNOME Terminal 2.28.1 in Ubuntu 9.10.

I would be greatful for any advice.

thanks,
paul

In GNU Emacs 23.1.1 (i486-pc-linux-gnu, GTK+ Version 2.18.3)
  of 2009-11-10 on vernadsky, modified by Debian
configured using `configure  '--build=i486-linux-gnu' '--host=i486-linux-gnu' 
'--prefix=/usr' '--sharedstatedir=/var/lib' '--libexecdir=/usr/l\
ib' '--localstatedir=/var/lib' '--infodir=/usr/share/info' 
'--mandir=/usr/share/man' '--with-pop=yes' '--enable-locallisppath=/etc/emacs23:/et\
c/emacs:/usr/local/share/emacs/23.1/site-lisp:/usr/local/share/emacs/site-lisp:/usr/share/emacs/23.1/site-lisp:/usr/share/emacs/site-lisp:/usr\
/share/emacs/23.1/leim' '--with-x=yes' '--with-x-toolkit=gtk' 
'--with-toolkit-scroll-bars' 'build_alias=i486-linux-gnu' 'host_alias=i486-linux\
-gnu' 'CFLAGS=-DDEBIAN -g -O2' 'LDFLAGS=-g' 'CPPFLAGS=''

Important settings:
   value of $LC_ALL: nil
   value of $LC_COLLATE: nil
   value of $LC_CTYPE: nil
   value of $LC_MESSAGES: nil
   value of $LC_MONETARY: nil
   value of $LC_NUMERIC: nil
   value of $LC_TIME: nil
   value of $LANG: en_US.UTF-8
   value of $XMODIFIERS: nil
   locale-coding-system: utf-8-unix
   default-enable-multibyte-characters: t

Major mode: Lisp Interaction

Minor modes in effect:
   tooltip-mode: t
   tool-bar-mode: t
   menu-bar-mode: t
   file-name-shadow-mode: t
   global-font-lock-mode: t
   font-lock-mode: t
   global-auto-composition-mode: t
   auto-composition-mode: t
   auto-encryption-mode: t
   auto-compression-mode: t
   line-number-mode: t
   transient-mark-mode: t

Recent input:
ESC [ > 1 ; 2 2 0 2 ; 0 c ESC O B ESC O A ESC O B ESC
x r e p o r t - e m a c s - b u g RET

Recent messages:
("emacs" "-Q")
Starting Emacs daemon.
When done with this frame, type C-x 5 0
Font-lock mode will override any faces you set in this buffer

bug#5696: update

[Paul Madden]

I was wrong that this only happens once per daemon invocation: I've been
noticing that, even with the same daemon process running, the first key input is
sometimes misinterpreted by "emacsclient -t file", printing weird characters in
the buffer instead of taking the action bound to the key. In this case, my F9 is
bound to goto-line, and emacsclient inserts "20~" in the buffer when I press it,
if it is the first keypress.

After this happens once, I can C-x C-x (or C-x #) to exit, "emacsclient -t file"
again, and F9 invokes goto-line correctly. I can do this several times in a row
without problem. But if I wait about a minute, not using emacs in the meantime,
and "emacsclient -t file" again, F9 misbehaves again.

paul

bug#5696: 23.1; emacsclient misinterprets (?) keys on first use

[Chong Yidong]

> I start the emacs daemon as "emacs -Q --daemon" and then run
> "emacsclient -t file". The four cursor-movement keys, as well as
> page-up and page-down, seem to be misinterpreted if one of them is the
> first key pressed in emacsclient. For example, page-down inserts the
> text "6~" in the buffer if it is the first key pressed in emacsclient
> after the emacs daemon is started. The down arrow key causes the
> following message to appear in the minibuffer: "Font-lock mode will
> override any faces you set in this buffer". Right arrow says: "M-o C
> is undefined".

Thanks for the bug report.  I believe this problem has already been
fixed in the repository; the fix will be included in the upcoming 23.2
release.