From: Juri Linkov <juri@linkov.net>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: E Sabof <esabof@gmail.com>, 13752@debbugs.gnu.org
Subject: bug#13752: Suggestions regarding the minibuffer
Date: Mon, 31 May 2021 23:13:03 +0300 [thread overview]
Message-ID: <87v96ylmew.fsf@linkov.net> (raw)
In-Reply-To: <87zgwbidqs.fsf@gnus.org> (Lars Ingebrigtsen's message of "Mon, 31 May 2021 09:06:19 +0200")
>> 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.
>
> Hm. I thought that the introduction of `set-message-function' would
> allow users to filter messages like this, but
>
> (setq set-message-function (lambda (string)
> 'no))
>
> only seems to inhibit messages from `message', not from `signal'? I'm
> having some difficulty tracing the logic here... Anybody know whether
> this is by design?
This looks like a new feature request :-) If this can't be implemented
using the existing signal-hook-function or signaling-function,
maybe then a new set-signal-function could be added?
next prev parent reply other threads:[~2021-05-31 20:13 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
2021-05-31 7:06 ` Lars Ingebrigtsen
2021-05-31 20:13 ` Juri Linkov [this message]
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=87v96ylmew.fsf@linkov.net \
--to=juri@linkov.net \
--cc=13752@debbugs.gnu.org \
--cc=esabof@gmail.com \
--cc=larsi@gnus.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 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).