From: Paul Pogonyshev <pogonyshev@gmail.com>
To: Michael Albinus <michael.albinus@gmx.de>
Cc: 57800-done@debbugs.gnu.org, Lars Ingebrigtsen <larsi@gnus.org>
Subject: bug#57800: TRAMP insert-file-contents now fails for regions
Date: Fri, 30 Sep 2022 22:48:29 +0200 [thread overview]
Message-ID: <CAG7Bpap316O72XdV_e1yD-9MmMDJ6P6ieSSh2wB2tob6XcuGuw@mail.gmail.com> (raw)
In-Reply-To: <87h70ofxck.fsf@gmx.de>
[-- Attachment #1: Type: text/plain, Size: 1500 bytes --]
Thanks. I suggest also adding a simple "version" to the cache. Whenever you
make an incompatible change in the future, bump this version. And also make
Tramp automatically discard all cached values when they come from a
different (earlier or even a later) version. Otherwise something like this
will certainly happen again sooner or later and will cost both the person
bumping into it and you or whoever responds to the bugreport a lot of time
again.
Paul
On Fri, 30 Sept 2022 at 21:58, Michael Albinus <michael.albinus@gmx.de>
wrote:
> Version: 29.1
>
> Michael Albinus <michael.albinus@gmx.de> writes:
>
> Hi Paul,
>
> >> Yes, that fixes the problem. Does that mean I somehow have a mixup of
> >> sources from different commits (not sure how) or that the cache is
> >> persistent and can survive long times? Note that I also run Emacs 28
> >> from time to time. Could it be that 29 reuses cache created by 28 that
> >> contains no-longer-compatible values?
> >
> > Could be the latter, yes. "tmpdir" is the only cache value I know of
> > which has changed its meaning(*). Perhaps I shall add a test that it
> > ignores cached "tmpdir" values if they are remote. But hmm, it has
> > changed its meaning also in Tramp 2.5.3.2, which is distributed via GNU
> > ELPA.
>
> Pushed this change to the emacs-28 branch, it will appear in the master
> branch after merge.
>
> It will also be contained in the upcoming Tramp 2.5.3.4 on GNU
> ELPA. Closing the bug.
>
> >> Paul
>
> Best regards, Michael.
>
[-- Attachment #2: Type: text/html, Size: 2053 bytes --]
next prev parent reply other threads:[~2022-09-30 20:48 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-14 12:11 bug#57800: TRAMP insert-file-contents now fails for regions Paul Pogonyshev
2022-09-14 18:08 ` Lars Ingebrigtsen
2022-09-14 18:18 ` Paul Pogonyshev
2022-09-14 18:23 ` Lars Ingebrigtsen
2022-09-14 18:33 ` Paul Pogonyshev
2022-09-15 10:30 ` Michael Albinus
2022-09-16 9:37 ` Lars Ingebrigtsen
2022-09-29 9:24 ` Paul Pogonyshev
2022-09-29 10:43 ` Lars Ingebrigtsen
2022-09-29 11:26 ` Paul Pogonyshev
2022-09-29 11:27 ` Paul Pogonyshev
2022-09-29 17:39 ` Michael Albinus
2022-09-30 8:49 ` Paul Pogonyshev
2022-09-30 18:39 ` Michael Albinus
2022-09-30 18:52 ` Paul Pogonyshev
2022-09-30 19:11 ` Michael Albinus
2022-09-30 19:58 ` Michael Albinus
2022-09-30 20:48 ` Paul Pogonyshev [this message]
2022-10-01 15:18 ` Michael Albinus
2022-10-01 16:16 ` Paul Pogonyshev
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=CAG7Bpap316O72XdV_e1yD-9MmMDJ6P6ieSSh2wB2tob6XcuGuw@mail.gmail.com \
--to=pogonyshev@gmail.com \
--cc=57800-done@debbugs.gnu.org \
--cc=larsi@gnus.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 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).