all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Tim Visher <tim.visher@gmail.com>
To: Luca Ferrari <fluca1978@gmail.com>
Cc: help-gnu-emacs <help-gnu-emacs@gnu.org>
Subject: Re: cannot ssh edit a file
Date: Sun, 21 Feb 2021 09:26:49 -0500	[thread overview]
Message-ID: <CAHa53uzOOMo6EOYse16PLbKRSOBrGP--dUiGDpeh99G33EDObA@mail.gmail.com> (raw)
In-Reply-To: <CAKoxK+7B8ebA-r-HFBes3kG0rbfZ-0GRV9oU_vfB8QV3hA2+XQ@mail.gmail.com>

On Sun, Feb 21, 2021 at 4:56 AM Luca Ferrari <fluca1978@gmail.com> wrote:

> On Sat, Feb 20, 2021 at 4:45 PM Tim Visher <tim.visher@gmail.com> wrote:
> >
> > Can you reproduce the problem from `emacs -Q`?
>
>
> Apparently this works a little better: it does not freeze on the colon
> typing, but when I try to open a file the minibuffer keeps saying
> "Waiting for prompts from remote shell..." and the connection is not
> established. This happens both with remote users that have zsh or sh
> as login shells.
> The only difference is that with sh as default shell, the minibuffer
> says "Tramp: Found remote shell prompt on miguel" (miguel being the
> remote host) and nothing happens, no connection is made.
> I've inspected connections from the remote host point of view, and
> there is no ssh connection reported by netstat.
>

So from `emacs -Q` did you apply Óscar's advice regarding setting the TRAMP
verbosity level? This feels likely to be an ssh configuration problem on
either the local end (in ~/.ssh/config etc.) or on the remote end in your
shell init files. TRAMP can be particularly difficult to debug in this kind
of situation, though.

My post about how to only customize your prompt when the shell is
interactive may be interesting to you as well.
https://blog.twonegatives.com/post/615830090370187264/effective-emacs-how-to-have-your-fancy-prompt-and


  reply	other threads:[~2021-02-21 14:26 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-20  9:43 cannot ssh edit a file Luca Ferrari
2021-02-20 13:21 ` Leo Butler
2021-02-20 15:22   ` Luca Ferrari
2021-02-20 15:42     ` Luca Ferrari
2021-02-20 15:45 ` Tim Visher
2021-02-20 16:35   ` Óscar Fuentes
2021-02-21  9:55   ` Luca Ferrari
2021-02-21 14:26     ` Tim Visher [this message]
2021-02-21 15:30     ` Michael Albinus
2021-02-22  7:59       ` Luca Ferrari
2021-02-22  8:38         ` Michael Albinus
2021-02-22 14:56           ` Luca Ferrari
2021-02-22 15:06             ` Michael Albinus
2021-02-22 16:00               ` Luca Ferrari
2021-02-22 16:45                 ` Tim Visher
2021-02-22 17:37                   ` Michael Albinus
2021-02-22 18:54                     ` Tim Visher
2021-02-23  8:19                       ` Luca Ferrari
2021-02-23 15:44                         ` Tim Visher
2021-02-23 16:25                           ` Luca Ferrari
2021-02-23 16:37                             ` Tim Visher
2021-02-23 16:44                               ` Michael Albinus
2021-03-15 15:56                                 ` Luca Ferrari
2021-03-15 16:27                                   ` Michael Albinus
2021-03-18 10:40                                     ` Luca Ferrari
2021-03-18 11:57                                       ` Michael Albinus
2021-02-23 16:40                           ` 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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAHa53uzOOMo6EOYse16PLbKRSOBrGP--dUiGDpeh99G33EDObA@mail.gmail.com \
    --to=tim.visher@gmail.com \
    --cc=fluca1978@gmail.com \
    --cc=help-gnu-emacs@gnu.org \
    /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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.