From: Jarek Czekalski <jarekczek@poczta.onet.pl>
To: emacs-devel@gnu.org
Subject: Re: Request: Use message instead of message_with_string for user visible output?
Date: Mon, 28 Oct 2013 09:04:58 +0100 [thread overview]
Message-ID: <526E1AAA.9060308@poczta.onet.pl> (raw)
In-Reply-To: <CADkJX2j+3VvqRoom5Wxsa1mGPTKLQmyh8-4EkTj-RVK=cfZ+6Q@mail.gmail.com>
W dniu 2013-10-27 23:07, T.V. Raman pisze:
> My personal preference
> would be to not to muck with command-error-function -- I played
> with it a bit last week -- it feels like too heavy a hammer, and
> at the end of the day might also produce too much output.
Raman, in this thread [1] we are given green light to improve
command-error-function. Could you provide an example of the operation,
that would be handled badly by command-error-function? For me it seems
to be the best solution. For example it delivers "read only" message
properly.
Further, if "key undefined" was also populated as an error-message, it
would not require special handling by Emacspeak. This is all a song of
the future (Emacs 25), but why not having a good plan?
By now you could start using command-error-function as if it was our
private variable, later it would be made better accessible for packages
and then we would adjust to new standards.
Jarek
[1]
http://emacs.1067599.n5.nabble.com/command-error-function-default-handler-tp300931.html
next prev parent reply other threads:[~2013-10-28 8:04 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-26 16:11 Request: Use message instead of message_with_string for user visible output? T.V. Raman
2013-10-26 16:21 ` Eli Zaretskii
2013-10-26 16:33 ` T.V. Raman
2013-10-26 19:47 ` Dmitri Paduchikh
2013-10-27 22:07 ` T.V. Raman
2013-10-28 2:06 ` Richard Stallman
2013-10-28 8:04 ` Jarek Czekalski [this message]
2013-10-28 18:53 ` Johan Bockgård
2013-10-29 1:27 ` T.V. Raman
2013-10-29 1:26 ` T.V. Raman
2013-10-26 17:16 ` Drew Adams
2013-10-26 18:41 ` Stefan Monnier
2013-10-27 22:03 ` T.V. Raman
2013-10-29 20:54 ` Stefan Monnier
2013-10-30 9:17 ` 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=526E1AAA.9060308@poczta.onet.pl \
--to=jarekczek@poczta.onet.pl \
--cc=emacs-devel@gnu.org \
/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.