From: Juanma Barranquero <lekktu@gmail.com>
To: martin rudalics <rudalics@gmx.at>
Cc: Emacs developers <emacs-devel@gnu.org>
Subject: Re: Delayed warnings
Date: Mon, 21 Mar 2011 15:48:54 +0100 [thread overview]
Message-ID: <AANLkTinJ2+uTTNQkyG4K747i+ZMnqQxs9NQNdWrz1=TQ@mail.gmail.com> (raw)
In-Reply-To: <4D874FF3.9010606@gmx.at>
On Mon, Mar 21, 2011 at 14:17, martin rudalics <rudalics@gmx.at> wrote:
> Fully agreed. But the same arguments hold for redisplay errors which
> currently pass through add_to_log where they are treated like messages.
Of course there's a hierarchy of "errors": those that the user cannot
do anything about (and should go to *Messages*), those that the user
*must* attend to (and should either interrupt the user or bring Emacs
to a halt), and warnings that inform the user about what he should
do/know, but can be ignored.
I'm mostly concerned about the third kind, specially when they happen
in low-level code, because they are difficult to make (from C) both
visible and, user wishing, easily ignorable. Sending them to
*Messages* is not enough, unless we're going to (pop-to-buffer
"*Messages*") and that's basically duplicating `display-warning' :-)
> What I wanted is a mechanism that handles (and optionally ignores) all
> sorts of errors/warnings which currently can't be issued prominently
> because Emacs is in an inconsistent state.
Which kind of design have you in mind?
Juanma
next prev parent reply other threads:[~2011-03-21 14:48 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-20 5:44 Delayed warnings Juanma Barranquero
2011-03-21 8:01 ` martin rudalics
2011-03-21 12:01 ` Juanma Barranquero
2011-03-21 13:17 ` martin rudalics
2011-03-21 13:43 ` Eli Zaretskii
2011-03-21 18:06 ` martin rudalics
2011-03-21 14:48 ` Juanma Barranquero [this message]
2011-03-21 18:06 ` martin rudalics
2011-03-21 20:19 ` Juanma Barranquero
2011-03-21 22:05 ` Stefan Monnier
2011-03-22 7:59 ` martin rudalics
2011-03-22 11:59 ` Juanma Barranquero
2011-03-23 13:50 ` Jeff Sparkes
2011-03-25 13:10 ` Juanma Barranquero
2011-04-27 0:55 ` Juanma Barranquero
2011-04-27 3:05 ` Eli Zaretskii
2011-04-27 11:27 ` Juanma Barranquero
2011-04-27 17:32 ` Stefan Monnier
2011-04-27 22:11 ` Juanma Barranquero
2011-04-28 0:40 ` Stefan Monnier
2011-04-28 0:59 ` Juanma Barranquero
2011-04-28 15:26 ` Stefan Monnier
2011-04-28 16:22 ` Juanma Barranquero
2011-04-28 18:39 ` Stefan Monnier
2011-05-08 17:58 ` Chong Yidong
2011-05-08 18:43 ` Juanma Barranquero
2011-05-09 14:15 ` Stefan Monnier
2011-05-09 18:28 ` Richard Stallman
2011-03-22 7:58 ` martin rudalics
2011-03-22 12:04 ` Juanma Barranquero
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='AANLkTinJ2+uTTNQkyG4K747i+ZMnqQxs9NQNdWrz1=TQ@mail.gmail.com' \
--to=lekktu@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=rudalics@gmx.at \
/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.