GNU bug report logs -
#5314
23.1; Inconsistent treatment of auto-save files
Previous Next
Reported by: Uday S Reddy <u.s.reddy <at> cs.bham.ac.uk>
Date: Tue, 5 Jan 2010 14:09:09 UTC
Severity: normal
Tags: fixed
Fixed in version 26.1
Done: Andrew Hyatt <ahyatt <at> gmail.com>
Bug is archived. No further changes may be made.
Full log
Message #17 received at submit <at> debbugs.gnu.org (full text, mbox):
Uday S Reddy wrote:
> I did some more testing of the functions after my initial report. The
> situation seems a lot more complex than I had imagined.
>
> With an old auto-save file on the disk, the following sequence done on
> a buffer seems to always return nil:
>
> (progn (insert "x") (recent-auto-save-p))
That could be explained by the dependencies on auto-save-interval and
auto-save-timeout. There is no guarantee that Emacs will auto-save
after the insert, regardless whether an old auto-save file exists.
> Killing the buffer in this case does not affect the old auto-save
> file.
>
> The following sequence seems to always return t
>
> (progn (set-buffer-modified-p t) (recent-auto-save-p))
Hmmm, that should also depend on auto-save-interval and auto-save-timeout.
> Killing the buffer in this case deletes the old auto-save file.
>
> So, it appears that recent-auto-save-p and kill-buffer are consistent
> with each other. But their behaviour is paradoxical with regard to
> set-buffer-modified-p.
--
Kevin Rodgers
Denver, Colorado, USA
This bug report was last modified 8 years and 172 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.