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 18:37:28 +0100 [thread overview]
Message-ID: <8735xoqa07.fsf@gmx.de> (raw)
In-Reply-To: <CAHa53uz60PWun0sO8+OaYVOz9EZmUBpDFnn8K3pH+ACW1ULUzA@mail.gmail.com> (Tim Visher's message of "Mon, 22 Feb 2021 11:45:12 -0500")
Tim Visher <tim.visher@gmail.com> writes:
> Based on the log here it looks like you are connecting to `luca@miguel
> ` and receiving back some odd text, namely:
>
> ```
> 16:56:45.839707 tramp-accept-process-output (10) # *tramp/ssh
> luca@miguel* run nil
> Last login: Mon Feb 22 15:58:27 2021 from n261732
> %
>
>
>
> [45mluca@miguel [49m [35m~ [37m % [39m [49m [?2004h
> ```
Indeed. Looks like zle prompt from zsh. Please read the Tramp manual
about.
Best regards, Michael.
next prev parent reply other threads:[~2021-02-22 17:37 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
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 [this message]
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=8735xoqa07.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).