From: "T.V. Raman" <tv.raman.tv@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>,
monnier@iro.umontreal.ca, emacs-devel@gnu.org
Subject: Info: Console Vs GUI difference?
Date: Fri, 1 Nov 2013 17:17:41 -0700 [thread overview]
Message-ID: <CADkJX2iJTJJUMSvhi-udvBqitoZCmHp_31g1ubWfUP6OqUz=zw@mail.gmail.com> (raw)
In-Reply-To: <837gcrc10q.fsf@gnu.org>
I understand better now. But I cannot but advice it because
there are many parts of emacs -- and emacs packages -- that
already use signal to display useful information to the user.
Yes, that is clearly incorrect, but that is what packages are
doing, so I have no option but to speak them. I'd be happy to
hear about an alternative -- note that I suspect
command-error-function might run into the same issue -- perhaps
differently.
--
--
On 11/1/13, Eli Zaretskii <eliz@gnu.org> wrote:
>> 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.
>
next prev parent reply other threads:[~2013-11-02 0:17 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
2013-11-02 0:17 ` T.V. Raman [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CADkJX2iJTJJUMSvhi-udvBqitoZCmHp_31g1ubWfUP6OqUz=zw@mail.gmail.com' \
--to=tv.raman.tv@gmail.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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.