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

Previous Next

Package: emacs;

Reported by: "Drew Adams" <drew.adams <at> oracle.com>

Date: Wed, 12 Dec 2012 18:48:01 UTC

Severity: wishlist

Tags: wontfix

Merged with 8180, 10726

Found in versions 24.0.50, 24.0.93, 24.3.50

Done: Lars Ingebrigtsen <larsi <at> gnus.org>

Bug is archived. No further changes may be made.

Full log

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

From: Eli Zaretskii <eliz <at> gnu.org>
To: Drew Adams <drew.adams <at> oracle.com>
Cc: 13159 <at> debbugs.gnu.org
Subject: Re: bug#13159: 24.3.50;
	`find-file-noselect' should not display or log messages
Date: Thu, 13 Dec 2012 19:27:31 +0200

> From: "Drew Adams" <drew.adams <at> oracle.com>
> Date: Wed, 12 Dec 2012 10:46:07 -0800
> 
> I'm using `find-file-noselect', and I see this in *Messages*:
>  
>  Note: file is write protected
>  
> First, that is not helpful at all, without saying WHICH file is
> write-protected.
>  
> More importantly, why does it make sense to display or record
> such a message when the file is not visited interactively?

If you invoke this function non-interactively, pass it a non-nil value
as the 2nd argument.  That should shut up any messages from this
function or the subroutines it calls.  E.g.:

  (find-file-noselect "/foo/bar/nonexistent-file" t)

    => #<buffer nonexistent-file>

and no messages.

Does this solve your problem?
This bug report was last modified 9 years and 23 days ago.

Previous Next

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