unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Michael Albinus <michael.albinus@gmx.de>
To: Luca Ferrari <fluca1978@gmail.com>
Cc: help-gnu-emacs <help-gnu-emacs@gnu.org>,
	Tim Visher <tim.visher@gmail.com>
Subject: Re: cannot ssh edit a file
Date: Mon, 22 Feb 2021 09:38:08 +0100	[thread overview]
Message-ID: <87eeh8qyz3.fsf@gmx.de> (raw)
In-Reply-To: <CAKoxK+7f0p64c5uHa6TL6M-sLFqH9cz+1KBSz54KhRekC4Z8RA@mail.gmail.com> (Luca Ferrari's message of "Mon, 22 Feb 2021 08:59:04 +0100")

Luca Ferrari <fluca1978@gmail.com> writes:

Hi Luca,

> I must be doing something wrong, since I've done (setq tramp-verbose
> 10) and evaluated the buffer, but nothing appeared anywhere (both with
> or without -Q startup).

For further analysis, we need the traces. Pls start

# emacs -Q --eval '(setq tramp-verbose 10)'

and run your test. After wards, there will be a buffer
*debug tramp/ssh host* which contains the traces.

> I've changed the shell from zsh to bash, I've changed the prompt
> according to suggestions to get a standard prompt, but the symptoms
> are the same.
> I've checked that logging into different machines works, so I've
> problem only with a FreeBSD host and a Fedora host that are currently
> not working fine.
> I've tried to ssh with or without keys but when Emacs has to open a
> file it freezes. I've also tried, as a desperate approach, to connect
> via IP instead of hostname, but nothing changed.
> What puzzles me is that I cannot see the connection established on the
> remote side.

I suspect it is a problem with your *local* prompt then.

> Luca

Best regards, Michael.



  reply	other threads:[~2021-02-22  8:38 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
2021-02-21 15:30     ` Michael Albinus
2021-02-22  7:59       ` Luca Ferrari
2021-02-22  8:38         ` Michael Albinus [this message]
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

  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=87eeh8qyz3.fsf@gmx.de \
    --to=michael.albinus@gmx.de \
    --cc=fluca1978@gmail.com \
    --cc=help-gnu-emacs@gnu.org \
    --cc=tim.visher@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.
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).