From: Michael Albinus <michael.albinus@gmx.de>
To: Stefan Kangas <stefan@marxist.se>
Cc: Lars Ingebrigtsen <larsi@gnus.org>,
41333-done@debbugs.gnu.org,
Philipp Stephani <p.stephani2@gmail.com>
Subject: bug#41333: 27.0.91; Spurious errors using TRAMP and auto-save-visited-mode
Date: Tue, 05 Jul 2022 18:54:41 +0200 [thread overview]
Message-ID: <875ykbbium.fsf@gmx.de> (raw)
In-Reply-To: <CADwFkmmkQb+kO7Mg7amQyeNqc2tBhD=b7C2R_og91miXaXk=BQ@mail.gmail.com> (Stefan Kangas's message of "Tue, 5 Jul 2022 06:11:22 -0700")
Stefan Kangas <stefan@marxist.se> writes:
Hi Stefan,
>> However, one possible counter measure is to disable
>> auto-save-visited-mode for remote files, as Philipp did in his
>> setup. Don't know whether this is acceptable, but given that we're
>> unsure whether Tramp works correctly here it might be the better option.
>
> I have added a user option 'auto-save-visited-remote-files' in commit
> 3631355dcb. It defaults to t for now, but we could perhaps consider
> changing it if this turns out to be a bigger problem.
Thanks! Given, that we have already remote-file-name-inhibit-cache and
remote-file-name-inhibit-locks, I propose to rename this new option to
remote-file-name-inhibit-auto-save-visited, with an inverted logic.
Best regards, Michael.
next prev parent reply other threads:[~2022-07-05 16:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-16 17:48 bug#41333: 27.0.91; Spurious errors using TRAMP and auto-save-visited-mode Philipp Stephani
2022-06-06 13:36 ` Lars Ingebrigtsen
2022-06-16 17:57 ` Philipp Stephani
2022-06-17 12:01 ` Lars Ingebrigtsen
2022-06-22 15:27 ` Michael Albinus
2022-07-05 13:11 ` Stefan Kangas
2022-07-05 16:54 ` Michael Albinus [this message]
2022-07-05 17:49 ` Stefan Kangas
2022-07-05 19:25 ` 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=875ykbbium.fsf@gmx.de \
--to=michael.albinus@gmx.de \
--cc=41333-done@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=p.stephani2@gmail.com \
--cc=stefan@marxist.se \
/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.