GNU bug report logs - #13159
24.3.50; `find-file-noselect' should not display or log messages

Previous Next

Full log

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

From: "Drew Adams" <drew.adams <at> oracle.com>
To: "'Juri Linkov'" <juri <at> jurta.org>
Cc: 13159 <at> debbugs.gnu.org
Subject: RE: bug#13159: 24.3.50;
	`find-file-noselect' should not display or log messages
Date: Wed, 12 Dec 2012 15:31:04 -0800

> > And there are umpteen additional such messages issued from 
> > this function.
> 
> There are umpteen messages issued from umpteen functions,
> all without a buffer's file name or other additional information.
> For example:
> 
> Auto-saving...done
> Mark set
> Follow the link [2 times]
> Type "q" to restore previous buffer.
> mouse-2, RET: find function's definition
> Mark saved where search started
> Entering debugger...
> Back to top level.
> Commands: d, x; RET; q to quit; ? for help.
> Making completion list...
> Quit
> Note: file is write protected
> Using vacuous schema
> 
> Do you want to fix all of them too?

Without looking at the details, it sounds like all of them should be fixed.

But this report is only about fixing messages wrt `find-file-noselect'.

Do you disagree that it makes little sense to display messages when
`find-file-noselect' is called from a non-interactive function?  And that it is
not too helpful to find a message in *Messages* telling you only that some
(unnamed) file (perhaps in a dolist that handles 12358 files) was
write-protected?

The priority of fixing bugs is for Emacs Dev to decide.  And this one has been
around a very long time, so it is probably not the most important.  But in any
case, it is a bug, no?

Previous Next

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