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: Sat, 02 Nov 2013 09:04:50 +0200 [thread overview]
Message-ID: <8338nfb7xp.fsf@gnu.org> (raw)
In-Reply-To: <CADkJX2iJTJJUMSvhi-udvBqitoZCmHp_31g1ubWfUP6OqUz=zw@mail.gmail.com>
> Date: Fri, 1 Nov 2013 17:17:41 -0700
> From: "T.V. Raman" <tv.raman.tv@gmail.com>
>
> 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.
I didn't say you shouldn't advise it. I just said that there's no bug
in Emacs in this case: it works as intended.
> 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.
The short-term alternative is to avoid speaking this particular
signal, by somehow detecting it.
The long-term alternative is to gradually abandon the advice methods
and switch to using special hooks that Emacs will provide for this
type of software. Please consider presenting a list of hooks you'd
like to have for Emacsspeak, and file a feature request bug report
with that list. Emacs ought to have good support for Emacsspeak that
does not require use of advice, IMO.
next prev parent reply other threads:[~2013-11-02 7:04 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
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 [this message]
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=8338nfb7xp.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).