From: Michael Albinus <michael.albinus@gmx.de>
To: Mani Kancherla <kancherla.mani@gmail.com>
Cc: 50205@debbugs.gnu.org
Subject: bug#50205: 27.2; crashes or hangs when opening a specific file using tramp
Date: Thu, 02 Sep 2021 09:22:00 +0200 [thread overview]
Message-ID: <87mtov5tnr.fsf@gmx.de> (raw)
In-Reply-To: <CAGaWTtD2VBs=p3_SZjQkFOx18GK1Z5hs2Ebhi53p4sMOq7O-3w@mail.gmail.com>
Mani Kancherla <kancherla.mani@gmail.com> writes:
> Hi Michael,
Hi Mani,
> Looks like the workaround for the installation issue is to run "M-x
> tramp-recompile-elpa", but it complains there is no such command. So,
> I just opened ~/.emacs.d/elpa/tramp-2.5.1.1/tramp.el in emacs and from
> the menu selected Emacs-Lisp> Byte-Compile This File. I am not sure if
> it does the same thing. After that I restarted emacs and M-x
> tramp-version shows 2.5.1.1. With this, I still see the problem (still
> hangs or crashes).
Byte-compiling tramp*.el files is right, but the problem is that Emacs
should not have loaded the built-in Tramp already. Tramp comes with the
file tramp-compat.el, which offers defsubsts and defmacros different for
Emacs versions. If Tramp is loaded already when byte-compiling, the
loaded version of tramp-compat.el would be used.
A recipe to cure this in your environment would be:
1. Remove all byte-compiled Tramp files.
# rm -f ~/.emacs.d/elpa/tramp-2.5.1.1/tramp*.elc
2. Start Emacs with Tramp's source files
# emacs -L ~/.emacs.d/elpa/tramp-2.5.1.1 -l tramp
This should not give you the error.
3. Recompile Tramp ELPA package *with this running Emacs instance*
M-x tramp-recompile-elpa
Now everything shall be fine, and if you start Emacs again, using the
Tramp ELPA package, there shouldn't be the error.
> Thanks,
> Mani
Best regards, Michael.
next prev parent reply other threads:[~2021-09-02 7:22 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-25 19:24 bug#50205: 27.2; crashes or hangs when opening a specific file using tramp Mani Kancherla
2021-08-26 6:26 ` Eli Zaretskii
[not found] ` <CAGaWTtCxKX8=qavjiubFrnMcQShBax86OM7SAeTmnHEmd6z-qA@mail.gmail.com>
2021-08-27 6:04 ` Eli Zaretskii
2021-08-27 6:51 ` Michael Albinus
2021-08-27 20:37 ` Mani Kancherla
2021-08-27 21:14 ` Mani Kancherla
2021-08-28 8:13 ` Michael Albinus
2021-08-28 21:26 ` Mani Kancherla
2021-08-29 7:23 ` Michael Albinus
2021-08-30 20:50 ` Mani Kancherla
2021-09-02 7:22 ` Michael Albinus [this message]
2021-09-03 16:44 ` Mani Kancherla
2021-09-04 7:06 ` Michael Albinus
2021-09-08 21:12 ` Mani Kancherla
2021-09-09 7:02 ` Michael Albinus
2021-09-09 16:41 ` Alan Third
2021-09-11 0:20 ` Mani Kancherla
2021-09-11 8:06 ` Michael Albinus
2021-09-15 0:55 ` Mani Kancherla
2021-09-15 6:52 ` Alan Third
2021-09-17 21:01 ` Mani Kancherla
2021-09-18 7:07 ` Michael Albinus
2021-09-18 7:52 ` Michael Albinus
2021-09-24 20:39 ` Mani Kancherla
2021-10-05 16:40 ` Mani Kancherla
2021-10-06 7:18 ` Michael Albinus
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=87mtov5tnr.fsf@gmx.de \
--to=michael.albinus@gmx.de \
--cc=50205@debbugs.gnu.org \
--cc=kancherla.mani@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).