From: Stefan Kangas <stefan@marxist.se>
To: Michael Albinus <michael.albinus@gmx.de>
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, 5 Jul 2022 06:11:22 -0700 [thread overview]
Message-ID: <CADwFkmmkQb+kO7Mg7amQyeNqc2tBhD=b7C2R_og91miXaXk=BQ@mail.gmail.com> (raw)
In-Reply-To: <87r13goh0y.fsf@gmx.de> (Michael Albinus's message of "Wed, 22 Jun 2022 17:27:09 +0200")
Michael Albinus <michael.albinus@gmx.de> writes:
> I'm sorry but w/o any more information I don't know what I could do
> else. Perhaps we should close the bug, although it is not satisfying w/o
> knowing what is/was up.
I think this might make sense for now. If someone runs into it again,
they can open a new bug.
> 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.
With that, I'm closing this bug.
next prev parent reply other threads:[~2022-07-05 13:11 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 [this message]
2022-07-05 16:54 ` Michael Albinus
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
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='CADwFkmmkQb+kO7Mg7amQyeNqc2tBhD=b7C2R_og91miXaXk=BQ@mail.gmail.com' \
--to=stefan@marxist.se \
--cc=41333-done@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=michael.albinus@gmx.de \
--cc=p.stephani2@gmail.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.
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).