GNU bug report logs - #12849
24.2.50; Doc: `message': mention `message-log-max'

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 12849 in the body.
You can then email your comments to 12849 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: Michael Heerdegen <michael_heerdegen <at> web.de>
To: bug-gnu-emacs <at> gnu.org
Subject: 24.2.50; Doc: `message': mention `message-log-max'
Date: Sat, 10 Nov 2012 01:14:04 +0100

Hi,

I made the experience that many people don't know that logging messages
(printed with `message') in the *Messages* buffer can be prevented with
binding `message-log-max' to nil.

Indeed, it's not easy to find in the doc, and the name `message-log-max'
also doesn't sound as if this variable could have this effect.

I think we should mention this effect of binding `message-log-max' to
nil in the docstring of `message', e.g. by changing this sentence:

The message also goes into the `*Messages*' buffer.

to

The message also goes into the `*Messages*' buffer if `message-log-max'
is not nil.


Thanks,

Michael.


In GNU Emacs 24.2.50.1 (x86_64-pc-linux-gnu, GTK+ Version 3.4.2)
 of 2012-11-01 on dex, modified by Debian
 (emacs-snapshot package, version 2:20121101-1)
Windowing system distributor `The X.Org Foundation', version 11.0.10707000
System Description:	Debian GNU/Linux testing (wheezy)

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

From: Leo <sdl.web <at> gmail.com>
To: bug-gnu-emacs <at> gnu.org
Subject: Re: bug#12849: 24.2.50; Doc: `message': mention `message-log-max'
Date: Sat, 10 Nov 2012 12:51:32 +0800

On 2012-11-10 08:14 +0800, Michael Heerdegen wrote:
> I made the experience that many people don't know that logging messages
> (printed with `message') in the *Messages* buffer can be prevented with
> binding `message-log-max' to nil.

How about adding:

(defsubst message-nolog (format-string &rest args)
  "Same as `message' except not writing to *Messages* buffer."
  (let (message-log-max) (apply 'message format-string args)))

This could encourage elisp authors to choose what to log to *Messages*
buffer. For example, ff-quiet-mode defaults to nil and, boy, this
library can write thousands of useless lines to *Messages* buffer.

Leo

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

From: Michael Heerdegen <michael_heerdegen <at> web.de>
To: Leo <sdl.web <at> gmail.com>
Cc: 12849 <at> debbugs.gnu.org
Subject: Re: bug#12849: 24.2.50; Doc: `message': mention `message-log-max'
Date: Sat, 10 Nov 2012 17:51:24 +0100

Leo <sdl.web <at> gmail.com> writes:

> How about adding:
>
> (defsubst message-nolog (format-string &rest args)
>   "Same as `message' except not writing to *Messages* buffer."
>   (let (message-log-max) (apply 'message format-string args)))
>
> This could encourage elisp authors to choose what to log to *Messages*
> buffer. For example, ff-quiet-mode defaults to nil and, boy, this
> library can write thousands of useless lines to *Messages* buffer.

I would appreciate something like that (besides improving the doc).

Maybe the same could be done for `with-temp-message'.


Regards,

Michael. 

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

From: Glenn Morris <rgm <at> gnu.org>
To: 12849-done <at> debbugs.gnu.org
Subject: Re: bug#12849: 24.2.50; Doc: `message': mention `message-log-max'
Date: Thu, 15 Nov 2012 21:42:04 -0500

Version: 24.3

Michael Heerdegen wrote:

> I think we should mention this effect of binding `message-log-max' to
> nil in the docstring of `message'

Thanks; done.

Previous Next

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