From: Stefan Monnier <monnier@IRO.UMontreal.CA>
Cc: emacs-devel@gnu.org
Subject: Re: auto-save-visited-file-name
Date: 17 Oct 2003 17:14:59 -0400 [thread overview]
Message-ID: <jwvd6cvo9ie.fsf-monnier+emacs/devel@vor.iro.umontreal.ca> (raw)
In-Reply-To: <E1AAbUM-0000kC-1H@fencepost.gnu.org>
> Does this solve the problems you found with auto-save-visited-file-name?
It helps, but see below.
> *** buffer.c.~1.438.~ Thu Sep 11 09:51:05 2003
> --- buffer.c Fri Oct 17 11:37:36 2003
> ***************
> *** 1429,1435 ****
> if (STRINGP (b->auto_save_file_name)
> && b->auto_save_modified != 0
> && BUF_SAVE_MODIFF (b) < b->auto_save_modified
> ! && BUF_SAVE_MODIFF (b) < BUF_MODIFF (b))
> {
> Lisp_Object tem;
> tem = Fsymbol_value (intern ("delete-auto-save-files"));
> --- 1429,1436 ----
> if (STRINGP (b->auto_save_file_name)
> && b->auto_save_modified != 0
> && BUF_SAVE_MODIFF (b) < b->auto_save_modified
> ! && BUF_SAVE_MODIFF (b) < BUF_MODIFF (b)
> ! && NILP (Fsymbol_value (intern ("auto-save-visited-file-name"))))
> {
> Lisp_Object tem;
> tem = Fsymbol_value (intern ("delete-auto-save-files"));
I think the above has a problem: auto-save-visited-file-name is only
consulted when setting up buffer-auto-save-file-name, so it can have a value
inconsistent with the actual situation. Better check whether
buffer-auto-save-file-name is equal to buffer-file-name.
Stefan
next prev parent reply other threads:[~2003-10-17 21:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-15 18:59 auto-save-visited-file-name Stefan Monnier
2003-10-15 21:20 ` auto-save-visited-file-name Kim F. Storm
2003-10-16 17:10 ` auto-save-visited-file-name Stefan Monnier
2003-10-16 19:52 ` auto-save-visited-file-name Kim F. Storm
2003-10-16 7:19 ` auto-save-visited-file-name Eli Zaretskii
2003-10-17 20:46 ` auto-save-visited-file-name Richard Stallman
2003-10-17 21:14 ` Stefan Monnier [this message]
2003-10-23 15:55 ` auto-save-visited-file-name Kevin Rodgers
2003-10-24 5:16 ` auto-save-visited-file-name Richard Stallman
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=jwvd6cvo9ie.fsf-monnier+emacs/devel@vor.iro.umontreal.ca \
--to=monnier@iro.umontreal.ca \
--cc=emacs-devel@gnu.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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).