unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Jacob Faibussowitsch <jacob.fai@gmail.com>
Cc: 55247@debbugs.gnu.org
Subject: bug#55247: [29.0.50; TRAMP] Tramp Always Thinks Buffer Changed On Disk After Edit -> Save
Date: Thu, 05 May 2022 13:16:40 +0200	[thread overview]
Message-ID: <87ilqktejr.fsf@gnus.org> (raw)
In-Reply-To: <B9FA9109-183D-4364-A0F2-3AA33BE72B9A@gmail.com> (Jacob Faibussowitsch's message of "Tue, 3 May 2022 11:55:40 -0500")

Jacob Faibussowitsch <jacob.fai@gmail.com> writes:

> The next time I try to edit the file. I know for a fact that the file
> has not changed, as I have compared copies of the file:

[...]

> $ diff file.c file_tmp.c

Changing the timestamp may also trigger the "really edit the buffer"
message.  Have you checked that something isn't altering the timestamp
of the file on the remote system?

> $ emacs -Q /ssh:<ssh alias>:path/to/file
> ```
> 2. Change something
> 3. C-x C-s
> 4. Try to change something else
> 5.
> ```
> <file name> changed on disk; really edit the buffer? (y, n, r or C-h)

I'm unable to reproduce this problem in Emacs 29.

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no





  reply	other threads:[~2022-05-05 11:16 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 [this message]
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
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

  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=87ilqktejr.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=55247@debbugs.gnu.org \
    --cc=jacob.fai@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).