GNU bug report logs -
#63633
Emacs becomes unresponsive when trying to ssh into localhost (MacOS)
Previous Next
Reported by: Arteen Abrishami <arteen1000 <at> gmail.com>
Date: Sun, 21 May 2023 22:12:02 UTC
Severity: normal
Tags: notabug
Done: Michael Albinus <michael.albinus <at> gmx.de>
Bug is archived. No further changes may be made.
Full log
View this message in rfc822 format
[Message part 1 (text/plain, inline)]
Your message dated Tue, 23 May 2023 09:42:02 +0200
with message-id <877cszebp1.fsf <at> gmx.de>
and subject line Re: bug#63633: Emacs becomes unresponsive when trying to ssh into localhost (MacOS)
has caused the debbugs.gnu.org bug report #63633,
regarding Emacs becomes unresponsive when trying to ssh into localhost (MacOS)
to be marked as done.
(If you believe you have received this mail in error, please contact
help-debbugs <at> gnu.org.)
--
63633: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=63633
GNU Bug Tracking System
Contact help-debbugs <at> gnu.org with problems
[Message part 2 (message/rfc822, inline)]
[Message part 3 (text/plain, inline)]
I have a Linux VM that I ssh into from my MacOS machine. From the terminal, in shell, this looks like: `ssh user <at> localhost -p 2222`. This works.
I also am able to use tramp to ssh into a different machine. On the terminal, this looks like `ssh machinename`. For tramp I use `M-x dired <RET> /ssh:machinename:/home/user <RET>`.
I am trying to ssh into the localhost via emacs. I use `M-x dired <RET> /ssh:user <at> localhost#2222:/ <RET>`. This does not work. The message it will show is “Opening connection will for user <at> localhost using ssh…” forever.
Emacs will become unresponsive, and I will hear my fans very loudly. This continues for as long as I’ve let it. I have to Force Quit emacs. I am running GNU Emacs 30.0.50.
- Arteen
[Message part 4 (text/html, inline)]
[Message part 5 (message/rfc822, inline)]
Arteen Abrishami <arteen1000 <at> gmail.com> writes:
> Thanks. This works.
Thanks for the confirmation. Closing the bug.
> As an aside, I am finding that within the ssh session, inside eshell,
> if I update directory contents (via “rm” for example), it takes about
> 10 seconds for “ls” to recognize the fact that the file has been
> removed, and for the first few “ls” after removal it will note that
> the file is still there.
>
> Would this be a separate issue?
I cannot reproduce it here. Please check, which "rm" command you use,
you'll see it in the *eshell* buffer:
--8<---------------cut here---------------start------------->8---
~ $ which rm
eshell/rm is a byte-compiled Lisp function in ‘em-unix.el’.
--8<---------------cut here---------------end--------------->8---
If it is the same for you, please write a new bug report. Append the
contents of your *eshell* buffer in order to see the commands, and in
order to reproduce it locally.
Best regards, Michael.
This bug report was last modified 1 year and 361 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.