unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Manuel Giraud <manuel@ledu-giraud.fr>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 55247@debbugs.gnu.org, Michael Albinus <michael.albinus@gmx.de>,
	Jacob Faibussowitsch <jacob.fai@gmail.com>
Subject: bug#55247: [29.0.50; TRAMP] Tramp Always Thinks Buffer Changed On Disk After Edit -> Save
Date: Fri, 06 May 2022 13:17:25 +0200	[thread overview]
Message-ID: <87bkwa6hbu.fsf@elite.giraud> (raw)
In-Reply-To: <87levfnfba.fsf@gnus.org> (Lars Ingebrigtsen's message of "Fri, 06 May 2022 12:08:57 +0200")

Lars Ingebrigtsen <larsi@gnus.org> writes:

> Manuel Giraud <manuel@ledu-giraud.fr> writes:
>
>>> rm lisp/net/tramp*.elc; make
>>
>> Hi Michael,
>>
>> I've just rebuild emacs on current HEAD (with your fix) but I'm still
>> facing this issue. Would you need tramp trace for this?
>
> Is this after deleting the .elc files?  (Or a "make bootstrap" to make
> sure.)

Sorry my bad. It works after a "make bootstrap". Thanks Michael!

But how come emacs does not install the new .elc for a freshly patch .el
with a classical "make && make install"?
-- 
Manuel Giraud





  reply	other threads:[~2022-05-06 11:17 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
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 [this message]
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=87bkwa6hbu.fsf@elite.giraud \
    --to=manuel@ledu-giraud.fr \
    --cc=55247@debbugs.gnu.org \
    --cc=jacob.fai@gmail.com \
    --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).