From: Richard Stallman <rms@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: [Emacs-commit] emacs/lisp saveplace.el
Date: Tue, 31 May 2005 00:18:21 -0400 [thread overview]
Message-ID: <E1DcyCr-00060K-Vd@fencepost.gnu.org> (raw)
In-Reply-To: <87d5r9e9op.fsf@floss.red-bean.com> (message from Karl Fogel on Sun, 29 May 2005 21:20:38 -0500)
What were the bad effects of using 'write-file'?
It made saveplace act as if the user had visited this file,
so that the next session would restore the place.
I ask because I'm wondering if the same change should be made to
'bookmark-write-file' in bookmark.el.
If bookmark.el currently visits the file when reading it,
changing the way it writes the file would not alter the outcome.
In fact, maybe there should be a bigger change to bookmark-write-file.
Instead of using find-file-noselect, it could just work the way
save-place-alist-to-file does: switch to a buffer, clear the buffer,
insert the new data, and write it out to the destination. That is:
How often do users visit the bookmark file? If they do this commonly,
then it is better to visit the file. If they do this quite rarely,
then could be is better to work like save-place-alist-to-file.
Another alternative, which could be best if you want Emacs to make backups
of the bookmark file in the usual way, is to visit the file normally,
but kill the buffer after saving it, unless the buffer existed previously.
prev parent reply other threads:[~2005-05-31 4:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1DcJHX-00083Y-00@savannah.gnu.org>
2005-05-30 2:20 ` [Emacs-commit] emacs/lisp saveplace.el Karl Fogel
2005-05-31 4:18 ` Richard Stallman [this message]
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=E1DcyCr-00060K-Vd@fencepost.gnu.org \
--to=rms@gnu.org \
--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).