GNU bug report logs - #38737
26.3; Doc string of `files--message'

Previous Next

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 38737 in the body.
You can then email your comments to 38737 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Drew Adams <drew.adams <at> oracle.com>
To: bug-gnu-emacs <at> gnu.org
Subject: 26.3; Doc string of `files--message'
Date: Tue, 24 Dec 2019 13:42:34 -0800 (PST)

Doc string:

"Like `message', except sometimes don't print to minibuffer.
If the variable `save-silently' is non-nil, the message is not
displayed on the minibuffer."

`message' does not "print to" the minibuffer or "display on" the
minibuffer.  It shows a message in the echo area.

Plus, it's not true that it sometimes does not show the message.  What
really happens is that the message is sometimes shown and then
immediately cleared - it is still logged in `*Messages*', for example.

The doc string should just say that if `save-silently' is non-nil then,
after showing the message in the echo area, it is cleared.



In GNU Emacs 26.3 (build 1, x86_64-w64-mingw32)
 of 2019-08-29
Repository revision: 96dd0196c28bc36779584e47fffcca433c9309cd
Windowing system distributor `Microsoft Corp.', version 10.0.17763
Configured using:
 `configure --without-dbus --host=x86_64-w64-mingw32
 --without-compress-install 'CFLAGS=-O2 -static -g3''

Message #10 received at 38737-done <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: Drew Adams <drew.adams <at> oracle.com>
Cc: 38737-done <at> debbugs.gnu.org
Subject: Re: bug#38737: 26.3; Doc string of `files--message'
Date: Wed, 25 Dec 2019 16:51:33 +0200

> Date: Tue, 24 Dec 2019 13:42:34 -0800 (PST)
> From: Drew Adams <drew.adams <at> oracle.com>
> 
> `message' does not "print to" the minibuffer or "display on" the
> minibuffer.  It shows a message in the echo area.

Thanks, I fixed the wording.

> Plus, it's not true that it sometimes does not show the message.  What
> really happens is that the message is sometimes shown and then
> immediately cleared - it is still logged in `*Messages*', for example.

"Don't show" doesn't imply "do nothing", so I see no problem here.

> The doc string should just say that if `save-silently' is non-nil then,
> after showing the message in the echo area, it is cleared.

That's a description of the implementation, so not useful: the source
is always available.  From the user POV I think the message is not
shown, because redisplay doesn't have an opportunity to kick in.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.