bug#11822: 24.1; emacsclient terminal mode captures escape characters as text

[Ken Raeburn]

On 06/30/12 01:55, Eli Zaretskii wrote:
> > From: Ken Raeburn<raeburn@permabit.com>
> > Date: Fri, 29 Jun 2012 20:08:40 -0400
> >
> > I have no idea what the "error during redisplay" messages shown below
> > are about
> >      
> They come from safe_eval_handler, called by safe_eval when the Lisp
> expression it evaluates signals an error.  This is done because
> signaling an error in the usual way in this situation will re-renter
> redisplay, which will then again signal an error, etc.
>
> Can you find out which form causes this error?  This should be
> something like :eval form in something the display engine needs to
> evaluate, perhaps some part of the mode line.
>    

I finally ran into this one again, and tracked it down... in C mode I 
set header-line-format to hold:

  (which-func-mode ("" which-func-format))

and which-func-format uses which-func-current which evaluates

  (gethash (selected-window) which-func-table which-func-unknown)

but when my cursor is outside a function, which-func-table does contain 
an entry for the selected window, and the associated value is nil, which 
is not allowed at this point.  If I redefine which-func-current to use

  (or (gethash (selected-window) which-func-table nil)
        which-func-unknown)

then it displays "[???]" in my header line (which-func-unknown being set 
to "???"), as it should.  I don't know if it's intended that the window 
be listed in the hash with a nil value or not.


I still have not seen another occurrence of the original problem I 
reported, the control-sequence response winding up in the current buffer 
when I use emacsclient in terminal mode... I'll keep watching for it though.

Ken