From: Lars Magne Ingebrigtsen <larsi@gnus.org>
To: Bastien <bzg@altern.org>
Cc: 9139@debbugs.gnu.org
Subject: bug#9139: 24.0.50; Inappropriate warning: "File no longer exists!"
Date: Sun, 11 Sep 2011 04:52:29 +0200 [thread overview]
Message-ID: <m38vpv3i4y.fsf@stories.gnus.org> (raw)
In-Reply-To: <87d3h4t20s.fsf@gnu.org> (Bastien's message of "Thu, 21 Jul 2011 11:29:39 +0200")
Bastien <bzg@altern.org> writes:
> Emacs sends an inappropriate warning message when trying to
> find a file that isn't on the hardrive but is the filename of
> a buffer, thus somehow "existing" in Emacs.
>
> To reproduce the problem:
>
> emacs -Q
> C-x f ~/foo.txt
> C-x b bar
> C-x f ~/foo.txt
>
> => File no longer exists!
Yes, it shouldn't say anything in this instance.
But how? It's this code in files.el:
(cond ((not (file-exists-p filename))
(setq nonexistent t)
(message "File %s no longer exists!" filename))
Is there something stored in the buffer that's stored if the file once
has existed, but no longer exists? Let's see...
(visited-file-modtime)
=> (-1 65535)
in foo.txt. But is that a bug?
The doc string says:
Return the current buffer's recorded visited file modification time.
The value is a list of the form (HIGH LOW), like the time values
that `file-attributes' returns. If the current buffer has no recorded
file modification time, this function returns 0.
So I think that perhaps is should return 0?
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog http://lars.ingebrigtsen.no/
next prev parent reply other threads:[~2011-09-11 2:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-21 9:29 bug#9139: 24.0.50; Inappropriate warning: "File no longer exists!" Bastien
2011-07-21 10:17 ` Eli Zaretskii
2011-07-21 10:27 ` Bastien
2011-09-11 2:52 ` Lars Magne Ingebrigtsen [this message]
2011-09-11 6:00 ` Eli Zaretskii
2011-09-11 14:49 ` Lars Magne Ingebrigtsen
2011-09-11 18:57 ` Glenn Morris
2011-09-11 20:05 ` Eli Zaretskii
2011-09-11 23:32 ` bug#7547: Glenn Morris
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m38vpv3i4y.fsf@stories.gnus.org \
--to=larsi@gnus.org \
--cc=9139@debbugs.gnu.org \
--cc=bzg@altern.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.