unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: "T.V. Raman" <tv.raman.tv@gmail.com>
Cc: monnier@iro.umontreal.ca, emacs-devel@gnu.org
Subject: Re: Info: Console Vs GUI difference?
Date: Fri, 01 Nov 2013 22:36:37 +0200	[thread overview]
Message-ID: <837gcrc10q.fsf@gnu.org> (raw)
In-Reply-To: <CADkJX2i=BWJhk9JNBRCZpogi4yaGDi51Mj_fS=cNVhim_ESv9Q@mail.gmail.com>

> Date: Fri, 1 Nov 2013 13:24:47 -0700
> From: "T.V. Raman" <tv.raman.tv@gmail.com>
> 
> With all due respect, I believe you're  wrong here -- that's not
> the problem.  And it works correctly at the console.  When
> running under X, the signal once raised, gets raised repeatedly
> after every user command, and the backtrace shows that it's
> coming from redisplay.

It comes from redisplay because redisplay recomputes the menu and
tool-bar items.  As the tool bar is not displayed in a TTY session,
you don't get signals then.

The root cause is still that 'signal' is being advised in a way that
exposes it to the user.



  reply	other threads:[~2013-11-01 20:36 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-30  9:27 Info: Console Vs GUI difference? T.V. Raman
2013-10-30 12:35 ` Stefan Monnier
2013-10-30 21:46   ` T.V. Raman
2013-10-30 23:11     ` Stefan Monnier
2013-10-31 16:21       ` T.V. Raman
2013-10-31 18:02         ` Stefan Monnier
2013-10-31 22:14           ` T.V. Raman
2013-11-01  1:32             ` Stefan Monnier
2013-11-01  2:10               ` T.V. Raman
2013-11-01 12:23                 ` Stefan Monnier
2013-11-01 16:55                   ` T.V. Raman
2013-11-01 18:34                     ` Eli Zaretskii
2013-11-01 20:24                       ` T.V. Raman
2013-11-01 20:36                         ` Eli Zaretskii [this message]
2013-11-02  0:17                           ` T.V. Raman
2013-11-02  2:04                             ` Stefan Monnier
2013-11-03 15:51                               ` T.V. Raman
2013-11-03 19:02                                 ` Jarek Czekalski
2013-11-03 19:05                                   ` T.V. Raman
2013-11-03 21:19                                     ` Stefan Monnier
2013-11-04  3:10                                     ` Dmitri Paduchikh
2013-11-04 16:38                                       ` T.V. Raman
2013-11-02  7:04                             ` Eli Zaretskii
2013-11-02  1:39                           ` T.V. Raman
2013-11-02  8:06                             ` Jarek Czekalski
2013-11-02 15:35           ` T.V. Raman
2013-11-02 15:56             ` Jarek Czekalski
2013-11-02 16:35             ` Dmitri Paduchikh
2013-11-02 20:46               ` T.V. Raman
2013-10-30 13:46 ` Jarek Czekalski
2013-10-30 21:45   ` T.V. Raman
2013-10-31 20:23   ` Richard Stallman
2013-11-01  7:37     ` Eli Zaretskii
2013-11-01 17:21       ` T.V. Raman

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

  List information: https://www.gnu.org/software/emacs/

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

  git send-email \
    --in-reply-to=837gcrc10q.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    --cc=tv.raman.tv@gmail.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 public inbox

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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).