Subject: Re: bug#13159: 24.3.50; `find-file-noselect' should not display or log messages

From: Eli Zaretskii <[email-masked]>
Date: Thu, 13 Dec 2012 19:27:31 +0200

> From: "Drew Adams" <[email-masked]>
> 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?