all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Drew Adams <drew.adams@oracle.com>
Cc: 12515@debbugs.gnu.org
Subject: bug#12515: 24.2.50; Error during redisplay: (eval (mode-line-eol-desc)) signaled (quit)
Date: Tue, 25 Sep 2012 22:37:41 +0200	[thread overview]
Message-ID: <83r4pphm96.fsf@gnu.org> (raw)
In-Reply-To: <D5A77FBFC7D64AD2B85DFDAD182ED039@us.oracle.com>

> From: "Drew Adams" <drew.adams@oracle.com>
> Cc: <12515@debbugs.gnu.org>
> Date: Tue, 25 Sep 2012 13:22:40 -0700
> 
> > Do you remember what were you doing when this happened?  Is it
> > possible you typed "C-g"?
> 
> No.  But yes, it is possible that I hit `C-g'.

Unless you see a lot of these messages in *Messages*, I wouldn't worry
about this.

What happens is that as part of redisplay of the mode line, the
display engine calls the function mode-line-eol-desc (defined on
bindings.el), which produces the end-of-line (EOL) indicator near the
left edge of the mode line.  Because signaling an error normally
re-enters redisplay (to display the error message), the display code
suppresses the normal way of processing signals from Lisp it calls,
and instead intercepts all signals and adds this kind of message to
*Messages*.  Since mode-line-eol-desc does not disable quitting (maybe
it should), hitting C-g when it runs could cause this signal, I think.





  reply	other threads:[~2012-09-25 20:37 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-25 18:33 bug#12515: 24.2.50; Error during redisplay: (eval (mode-line-eol-desc)) signaled (quit) Drew Adams
2012-09-25 20:18 ` Eli Zaretskii
2012-09-25 20:22   ` Drew Adams
2012-09-25 20:37     ` Eli Zaretskii [this message]
2012-09-25 20:51       ` Drew Adams
2012-09-25 21:11         ` Eli Zaretskii

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=83r4pphm96.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=12515@debbugs.gnu.org \
    --cc=drew.adams@oracle.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.