unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Jim Porter <jporterbugs@gmail.com>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: michael.albinus@gmx.de, 55810@debbugs.gnu.org
Subject: bug#55810: 28.1; No "really edit the buffer?" prompt when editing a changed file over Tramp
Date: Sun, 5 Jun 2022 14:31:55 -0700	[thread overview]
Message-ID: <9ac561e4-2131-fa3a-7bcc-be329812ec9d@gmail.com> (raw)
In-Reply-To: <362c7432-b4ed-3ebf-7c20-109e11f4c8e8@gmail.com>

On 6/5/2022 1:25 PM, Jim Porter wrote:
> On 6/5/2022 1:04 PM, Lars Ingebrigtsen wrote:
>> I can reproduce this in Emacs 28.1, but not on the emacs-28 branch
>> (i.e., what will become Emacs 28.2).  Would it be possible for you to
>> test with that branch?
> 
> You're right, it looks like this is also fixed on the emacs-28 branch. 
> I'll try to bisect this (if only so that I write some defadvice to fix 
> it temporarily for 28.1) and report back if I find anything useful.

Ok, the commit that fixed this is 
93974198b62bea0350be503c8fc017e9d1a4542f, which is just a fixup commit 
after 009e88e002333b4090b021d24390c9137e5a2555. That commit updates 
Tramp to 2.5.3-pre, so I guess it was just a bug in the Tramp that 
shipped with 28.1.

However, I came across an interesting wrinkle. This is actually fixed in 
the GNU ELPA version of Tramp (currently 2.5.2.5). Installing this in 
Emacs 28.1 doesn't work correctly though, since v2.5.2.5 is "less" than 
the built-in Tramp version (v2.5.2.28.1). That explains why updating 
Tramp from GNU ELPA fixed the issue for me until I restarted Emacs. It 
loaded the fixed code temporarily, but then after restart, it chose the 
unfixed code because package.el thinks the built-in version is newer.

CC'ing Michael here. Maybe the easy solution is just to bump the GNU 
ELPA version of Tramp to 2.5.3 or something, and then package.el will 
recognize it as newer than what ships with 28.1.

For now, I have a workaround at least: I can just override the 
`load-path' to point to the newer Tramp version.





  reply	other threads:[~2022-06-05 21:31 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-05 18:43 bug#55810: 28.1; No "really edit the buffer?" prompt when editing a changed file over Tramp Jim Porter
2022-06-05 20:04 ` Lars Ingebrigtsen
2022-06-05 20:25   ` Jim Porter
2022-06-05 21:31     ` Jim Porter [this message]
2022-06-06  8:15       ` Michael Albinus
2022-06-07  4:23         ` Jim Porter

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=9ac561e4-2131-fa3a-7bcc-be329812ec9d@gmail.com \
    --to=jporterbugs@gmail.com \
    --cc=55810@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).