unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: manuel@ledu-giraud.fr
Cc: 62260@debbugs.gnu.org
Subject: bug#62260: 30.0.50; [PATCH] Restrict auto-save file mode
Date: Sat, 18 Mar 2023 22:21:03 +0200	[thread overview]
Message-ID: <837cvdbykw.fsf@gnu.org> (raw)
In-Reply-To: <838rftbzj3.fsf@gnu.org> (message from Eli Zaretskii on Sat, 18 Mar 2023 22:00:32 +0200)

> Cc: 62260@debbugs.gnu.org
> Date: Sat, 18 Mar 2023 22:00:32 +0200
> From: Eli Zaretskii <eliz@gnu.org>
> 
> > With this patch, the /tmp directory now contains an auto-save file with
> > mode 0600.
> 
> When a buffer visits a file, its auto-save file should have the same
> mode bits as the file itself (modulo your umask).  I see no need to
> affect that part in any case.  If the file itself is not private, why
> should its auto-save file be private?  Also, there's
> auto-save-visited-mode.

More generally: what problems are you trying to solve here?  If this
code causes some problems, please describe them, and let's see whether
and how we should fix them.

This code is in its present shape for the last 25 years at least, and
in all that time I don't think we ever had any complaints about the
mode bits of the auto-save files.  So if there's no real-life problem
here, I see no reason to change code that is stable for so long.





  reply	other threads:[~2023-03-18 20:21 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-18 15:18 bug#62260: 30.0.50; [PATCH] Restrict auto-save file mode Manuel Giraud via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-03-18 15:43 ` Eli Zaretskii
2023-03-18 18:39   ` Manuel Giraud via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-03-18 18:47     ` Eli Zaretskii
2023-03-18 18:51       ` Eli Zaretskii
2023-03-18 19:22         ` Manuel Giraud via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-03-18 20:00           ` Eli Zaretskii
2023-03-18 20:21             ` Eli Zaretskii [this message]
2023-03-19 11:43               ` Manuel Giraud via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-03-19 12:19                 ` Eli Zaretskii
2023-03-19 12:40                   ` Michael Albinus
2023-03-19 13:56                     ` Manuel Giraud via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-03-20 11:41                       ` Michael Albinus
2023-03-20 12:22                         ` Eli Zaretskii
2023-03-20 12:31                           ` Michael Albinus
2023-03-20 14:15                         ` Manuel Giraud via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-03-19 14:11                     ` Eli Zaretskii
2023-03-20 11:43                       ` Michael Albinus
2023-03-19 14:18                     ` Manuel Giraud via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-03-20 11:44                       ` Michael Albinus
2023-03-22 10:13                         ` Manuel Giraud via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-03-23 16:26                           ` Michael Albinus
2023-03-24  7:34                             ` Manuel Giraud via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-03-24 10:35                             ` Manuel Giraud via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-03-24 17:56                               ` Michael Albinus
2023-03-18 19:16       ` Manuel Giraud via Bug reports for GNU Emacs, the Swiss army knife of text editors

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=837cvdbykw.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=62260@debbugs.gnu.org \
    --cc=manuel@ledu-giraud.fr \
    /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).