all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Michael Albinus <michael.albinus@gmx.de>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 55247@debbugs.gnu.org, Manuel Giraud <manuel@ledu-giraud.fr>,
	Jacob Faibussowitsch <jacob.fai@gmail.com>
Subject: bug#55247: [29.0.50; TRAMP] Tramp Always Thinks Buffer Changed On Disk After Edit -> Save
Date: Thu, 05 May 2022 17:05:17 +0200	[thread overview]
Message-ID: <87y1zghvf6.fsf@gmx.de> (raw)
In-Reply-To: <87tua4niqr.fsf@gnus.org> (Lars Ingebrigtsen's message of "Thu, 05 May 2022 16:42:36 +0200")

Lars Ingebrigtsen <larsi@gnus.org> writes:

Hi,

> Manuel Giraud <manuel@ledu-giraud.fr> writes:
>
>> I'm also affected by this rather annoying bug when editing a file over
>> TRAMP. FWIW, I've just bisected it to this patch 47fe7a5983.
>
> Sorry; I was testing with an Emacs that was a couple days old.  With the
> current trunk, I can indeed reproduce the problem.  I'm also getting
> further errors:

I've seen this report, and it is already on my TODO. Just a matter of
available time to work on this.

Shall be fixed latest tomorrow, I hope.

Best regards, Michael.





  parent reply	other threads:[~2022-05-05 15:05 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-03 16:55 bug#55247: [29.0.50; TRAMP] Tramp Always Thinks Buffer Changed On Disk After Edit -> Save Jacob Faibussowitsch
2022-05-05 11:16 ` Lars Ingebrigtsen
2022-05-05 14:32   ` Manuel Giraud
2022-05-05 14:42     ` Lars Ingebrigtsen
2022-05-05 14:50       ` Jacob Faibussowitsch
2022-05-05 15:05       ` Michael Albinus [this message]
2022-05-06  8:43 ` Michael Albinus
2022-05-06  9:39   ` Manuel Giraud
2022-05-06  9:53     ` Michael Albinus
2022-05-06 10:08     ` Lars Ingebrigtsen
2022-05-06 11:17       ` Manuel Giraud
2022-05-06 11:22         ` Michael Albinus
2022-05-06 11:54           ` Manuel Giraud

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=87y1zghvf6.fsf@gmx.de \
    --to=michael.albinus@gmx.de \
    --cc=55247@debbugs.gnu.org \
    --cc=jacob.fai@gmail.com \
    --cc=larsi@gnus.org \
    --cc=manuel@ledu-giraud.fr \
    /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.