bug#63633: closed (Emacs becomes unresponsive when trying to ssh into localhost (MacOS))

[GNU bug Tracking System]

Your message dated Tue, 23 May 2023 09:42:02 +0200
with message-id <877cszebp1.fsf@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@gnu.org.)


-- 
63633: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=63633
GNU Bug Tracking System
Contact help-debbugs@gnu.org with problems

--- Begin Message --- Subject: Emacs becomes unresponsive when trying to ssh into localhost (MacOS) Date: Sun, 21 May 2023 15:11:37 -0700

I have a Linux VM that I ssh into from my MacOS machine. From the terminal, in shell, this looks like: `ssh user@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@localhost#2222:/ <RET>`. This does not work. The message it will show is “Opening connection will for user@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

--- End Message ---

> --- Begin Message ---
>
>
>
> Subject: 
>
> Re: bug#63633: Emacs becomes unresponsive when trying to ssh into localhost (MacOS)
>
>
>
>
> Date: 
>
> Tue, 23 May 2023 09:42:02 +0200
>
>
>
>
> User-agent: 
>
> Gnus/5.13 (Gnus v5.13)
>
>
>
>
> Arteen Abrishami <arteen1000@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.
>
>
> --- End Message ---