unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Manuel Giraud via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Michael Albinus <michael.albinus@gmx.de>
Cc: Eli Zaretskii <eliz@gnu.org>, 62260@debbugs.gnu.org
Subject: bug#62260: 30.0.50; [PATCH] Restrict auto-save file mode
Date: Fri, 24 Mar 2023 08:34:08 +0100	[thread overview]
Message-ID: <87sfduy55b.fsf@ledu-giraud.fr> (raw)
In-Reply-To: <875yaro2mm.fsf@gmx.de> (Michael Albinus's message of "Thu, 23 Mar 2023 17:26:25 +0100")

Michael Albinus <michael.albinus@gmx.de> writes:

> Manuel Giraud <manuel@ledu-giraud.fr> writes:
>
>> Hi Michael,
>
> Hi Manuel,
>
>> What do you think of the attached patch?
>
> Honestly, I haven't had enough time to review it in detail. My gut
> feeling tells me that it looks to complicate and too much hard-coded,
> but I will need to review. I hope I could do it next days.

Hi Michael,

Ok, I understand that.  My patch is a bit hard-coded you're right but I
think it will reduce false positive triggering the user prompt about
unsafe auto-save.

[...]

> Please take into account, that tramp-allow-unsafe-temporary-files is not
> only for auto-save files. It is used also for backup and file locks. See
> functions tramp-handle-find-backup-file-name, tramp-handle-lock-file and
> tramp-handle-make-auto-save-file-name.

Ok so it might not be possible to have this three state
'tramp-allow-unsafe-temporary-files' I propose.

> For the time being, I have added the possibility to suppress auto-save
> for remote files. The Tramp manual says now:

Thanks.  That looks great.  IIUC, with this, one can disable only
auto-save (not locking nor backup) on a per connection basis.  I guess
that it could replace what I was proposing then.
-- 
Manuel Giraud





  reply	other threads:[~2023-03-24  7:34 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
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 [this message]
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=87sfduy55b.fsf@ledu-giraud.fr \
    --to=bug-gnu-emacs@gnu.org \
    --cc=62260@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=manuel@ledu-giraud.fr \
    --cc=michael.albinus@gmx.de \
    /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).