From: Juri Linkov <juri@linkov.net>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: Keith David Bershatsky <esq@lawlist.com>, 19495@debbugs.gnu.org
Subject: bug#19495: 25.0.50; `message` -- optional argument to suppress echo area display
Date: Sun, 04 Aug 2019 22:14:17 +0300 [thread overview]
Message-ID: <87pnlkzxae.fsf@mail.linkov.net> (raw)
In-Reply-To: <87k1bvmidy.fsf@mouse.gnus.org> (Lars Ingebrigtsen's message of "Fri, 02 Aug 2019 22:17:45 +0200")
>> As a feature request, the Emacs team may wish to consider adding an
>> optional argument to the `message` function to permit suppression of
>> the message being displayed in the echo area.
>>
>> In my particular use case, there are certain process output strings
>> that I prefer having printed to the `*Messages*` buffer -- instead of
>> a dedicated process output buffer.
>
> [...]
>
>> The following is my workaround:
>>
>> (defun rsync-process-filter (proc string)
>> (let ((inhibit-read-only t))
>> (when (not (or
>> (string-match "files...\r" string)
>> (string-match "files to consider\n" string)))
>> (with-current-buffer (get-buffer-create "*Messages*")
>> (goto-char (point-max))
>> (insert string)))))
>
> (I'm going through old bug reports that unfortunately have not received
> any responses yet.)
>
> I kinda don't think extending `message' in this way would be ideal.
> Currently, `message' is pretty simple to understand, and to change it to
> not actually message anything (in some circumstances) would be
> confusing. Doing this in the way you've done in the workaround seems
> like a better idea.
Emacs 25 introduced a new variable 'inhibit-message' to suppress echo area display.
> So I'm closing this as a "wontfix".
This feature request was dated Jan 2015, and a new feature implemented
independently was added on Apr 2015.
prev parent reply other threads:[~2019-08-04 19:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-03 17:50 bug#19495: 25.0.50; `message` -- optional argument to suppress echo area display Keith David Bershatsky
2019-08-02 20:17 ` Lars Ingebrigtsen
2019-08-04 19:14 ` Juri Linkov [this message]
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=87pnlkzxae.fsf@mail.linkov.net \
--to=juri@linkov.net \
--cc=19495@debbugs.gnu.org \
--cc=esq@lawlist.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).