From: Sam Steingold <sds@gnu.org>
To: Michael Albinus <michael.albinus@gmx.de>
Cc: 49178@debbugs.gnu.org
Subject: bug#49178: 28.0.50; make-auto-save-file-name connects to remote
Date: Thu, 24 Jun 2021 14:30:08 -0400 [thread overview]
Message-ID: <CAFsbZ7bigFEiFL=uZEDuQRUhatwi4ZNi3t74GFm1OVAHzQX8WA@mail.gmail.com> (raw)
In-Reply-To: <87pmwbqhx1.fsf@gmx.de>
Hi Michael,
The doc for `tramp-allow-unsafe-temporary-files ` says:
>>> Whether root-owned auto-save or backup files can be written to "/tmp"
1. the file is not owned by root
2. `auto-save-list-file-prefix` is under my home, not /tmp
On Thu, 24 Jun 2021 at 13:41, Michael Albinus <michael.albinus@gmx.de> wrote:
>
> > When I edit a remote file using tramp (scp method), I notice a
> > significant slow-down on auto-save (not every time!), and a brief
> > investigation seems to indicate that make-auto-save-file-name MAY
> > re-establish the connection to the remote server when it is dead (or
> > something?)
>
> Well, this is the consequence of the fix for bug#45245. In etc/NEWS,
> this is mentioned as
>
> --8<---------------cut here---------------start------------->8---
> *** Writing sensitive auto-save or backup files to the local temporary
> directory must be confirmed. In order to suppress this confirmation,
> set user option 'tramp-allow-unsafe-temporary-files' to t.
> --8<---------------cut here---------------end--------------->8---
I am never asked for any confirmation.
--
Sam Steingold <http://sds.podval.org> <http://www.childpsy.net>
<http://steingoldpsychology.com>
next prev parent reply other threads:[~2021-06-24 18:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-22 20:53 bug#49178: 28.0.50; make-auto-save-file-name connects to remote Steingold
2021-06-24 17:41 ` Michael Albinus
2021-06-24 18:30 ` Sam Steingold [this message]
2021-06-24 18:37 ` Michael Albinus
2021-06-25 12:20 ` Michael Albinus
2021-07-07 18:39 ` Michael Albinus
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='CAFsbZ7bigFEiFL=uZEDuQRUhatwi4ZNi3t74GFm1OVAHzQX8WA@mail.gmail.com' \
--to=sds@gnu.org \
--cc=49178@debbugs.gnu.org \
--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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.