GNU bug report logs - #25653
25.1.91; buffer-file-name reports non-existing file

Previous Next

Package: emacs;

Reported by: Andreas Röhler <andreas.roehler <at> easy-emacs.de>

Date: Wed, 8 Feb 2017 09:01:02 UTC

Severity: minor

Tags: notabug, wontfix

Found in version 25.1.91

Done: Glenn Morris <rgm <at> gnu.org>

Bug is archived. No further changes may be made.

Full log


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

From: npostavs <at> users.sourceforge.net
To: Andreas Röhler <andreas.roehler <at> easy-emacs.de>
Cc: 25653 <at> debbugs.gnu.org
Subject: Re: bug#25653: 25.1.91; buffer-file-name reports non-existing file
Date: Wed, 08 Feb 2017 09:37:26 -0500
tags 25653 notabug
quit

Andreas Röhler <andreas.roehler <at> easy-emacs.de> writes:

> Emacs -Q
>
> Open some non-existing foo.py
>
> Before saving
>
> M-x buffer-file-name RET reports PATH-to/foo.py as buffer-file-name.
>
> IMO buffer-file-name only should get a value different from nil, if
> the buffer is connected with an existing file, as docu says:

> Return name of file BUFFER is visiting, or nil if none.

I disagree this is a bug, in `(emacs) Visiting' we see

   Successful visiting of any file, whether existing or not,

i.e., we can successfully visit a non-existing file.  Furthermore, the
existence of a file can change asynchronously, so it's not really
sensible to expect an Emacs variable to reflect that.  The state of
"visiting" just means that Emacs will write the buffer contents out to
the visited file when saved.




This bug report was last modified 8 years and 160 days ago.

Previous Next


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