From: Karl Kleinpaste <karl@jprc.com>
Subject: Re: Permissions of auto-save files (Re: permissions of dribble file)
Date: 13 Mar 1997 13:27:36 -0500 [thread overview]
Message-ID: <vxkwwrb4pgn.fsf@pocari-sweat.jprc.com> (raw)
In-Reply-To: Carsten Bormann's message of Thu, 13 Mar 1997 18:35:05 +0100 (MET)
Carsten Bormann <cabo@Informatik.Uni-Bremen.DE> writes:
> No -- that's not your dribble file, its the auto-save file of a
> not-yet-existing dribble file.
> Each time we install a new version of Emacs here, we apply the
> following patch:
...
> The real thing would be a way to indicate, from Emacs-Lisp, the
> desired privacy mode for auto-save files for each buffer in Emacs
> separately -- even those that don't have files yet (that's why I put
> bug-gnu-emacs into the CC).
Another alternative: Bury all auto-save files in a particular
directory, and then change the _directory_ mode to be 0700, thus
making irrelevant the question of what modes the files themselves
have.
(This also happens to be a major win when you're editing files in AFS
or NFS and your server departs this world for universes unknown.)
# mkdir ~/.auto
# chmod 700 ~/.auto
# cat >> .emacs
(defvar auto-save-dir "~/.auto/"
"directory for auto-saves. protected.")
(if (file-directory-p auto-save-dir)
(defun make-auto-save-file-name ()
"safe/fast place for auto-saves."
(interactive)
(concat auto-save-dir "#" (buffer-name (current-buffer)) "#")))
^D
next prev parent reply other threads:[~1997-03-13 18:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-03-13 17:10 permissions of dribble file John Palmieri
1997-03-13 17:35 ` Permissions of auto-save files (Re: permissions of dribble file) Carsten Bormann
1997-03-13 18:27 ` Karl Kleinpaste [this message]
1997-03-19 23:14 ` Danny Siu
1997-03-13 19:41 ` permissions of dribble file Edward J. Sabol
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=vxkwwrb4pgn.fsf@pocari-sweat.jprc.com \
--to=karl@jprc.com \
/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.
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 NNTP newsgroup(s).