From: Stefan Monnier <monnier@iro.umontreal.ca>
To: E Sabof <esabof@gmail.com>
Cc: 13752@debbugs.gnu.org
Subject: bug#13752: Suggestions regarding the minibuffer
Date: Mon, 18 Feb 2013 15:02:36 -0500 [thread overview]
Message-ID: <jwvd2vxv1hs.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <CAEp6DybUF7283D2xFZ_uhz3RVsKmnq-xEYFF-H-EbXrgLK0Spw@mail.gmail.com> (E. Sabof's message of "Mon, 18 Feb 2013 19:44:36 +0000")
> 1. Would it be possible to add a property to error symbols that would
> prevent the error message from appearing in the mini-buffer? I see
> little utility in messages such a "End of buffer", "Beginning of buffer"
> and "Text read-only".
> It could be seen as implementation logic leaking into UI.
I don't think these messages have anything to do with implementation.
Instead, they're present to explain to the user why nothing else
happened in response to their keypress.
As for your request, I would welcome a patch that makes the display of
error messages more flexible.
> 2. Could an option be created that wouldn't allow messages (regular or
> error) from being displayed, while the minibuffer is active and selected?
Not displaying them might not be the best default choice (tho an option
for it could be OK), but I'd welcome a patch that makes them less
intrusive (e.g. display the message at the end of the minibuffer, like
the " [No match]" message in completions).
Stefan
next prev parent reply other threads:[~2013-02-18 20:02 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-18 19:44 bug#13752: Suggestions regarding the minibuffer E Sabof
2013-02-18 20:02 ` Stefan Monnier [this message]
2021-05-31 7:06 ` Lars Ingebrigtsen
2021-05-31 20:13 ` Juri Linkov
2021-06-01 6:17 ` Lars Ingebrigtsen
2021-06-01 20:34 ` Juri Linkov
2021-06-02 5:46 ` Lars Ingebrigtsen
2021-06-02 12:32 ` Eli Zaretskii
2021-06-02 21:06 ` Juri Linkov
2021-06-03 7:30 ` Lars Ingebrigtsen
2021-06-03 20:29 ` Juri Linkov
2021-06-04 9:42 ` bug#42865: " Lars Ingebrigtsen
2021-06-04 16:27 ` Juri Linkov
2021-06-06 9:17 ` Lars Ingebrigtsen
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=jwvd2vxv1hs.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=13752@debbugs.gnu.org \
--cc=esabof@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).