From: Michael Albinus <michael.albinus@gmx.de>
To: Lennart Borgman <lennart.borgman@gmail.com>
Cc: 11065@debbugs.gnu.org
Subject: bug#11065: 24.0.94; Problem with tramp & plink
Date: Fri, 23 Mar 2012 08:48:39 +0100 [thread overview]
Message-ID: <871uojkbag.fsf@gmx.de> (raw)
In-Reply-To: <CAH8Pv0ibyFge=sA6DpOG3zy-j4ELRk6Npy_Ujs9Zpx-q-=97JQ@mail.gmail.com>
Lennart Borgman <lennart.borgman@gmail.com> writes:
Hi Lennart,
> Just a thought: Is not plink the "standard" way to communicate this
> way with Emacs on w32?
The problem is not related to plink. It can happen for every Tramp
connection using a remote shell, and the remote shell's prompt is
composed by "[]".
> Should perhaps this solution be documented somewhere?
Customizing `tramp-shell-prompt-pattern' is documented in the Tramp manual.
> (Or even implemented as a choice on w32?)
`tramp-shell-prompt-pattern' is derived from `shell-prompt-pattern'.
Both do not support "[]" style prompts, because shell script fragments like
if [ -n "$FOO" ]
would be treated as prompt. OTOH, Tramp redefines the prompt immediately
after connection, so it might be safe to add this prompt style (as I
have recommended to Dani).
I will check the Tramp sources, whether there are other potential
conflicts. If there is no obvious problem, I'll extend
`tramp-shell-prompt-pattern' in the trunk such a way, once it has been
reopened for 24.2. Let's see, whether somebody rants about.
Best regards, Michael.
next prev parent reply other threads:[~2012-03-23 7:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-22 10:54 bug#11065: 24.0.94; Problem with tramp & plink Dani Moncayo
2012-03-22 16:28 ` Michael Albinus
2012-03-22 16:41 ` Dani Moncayo
2012-03-22 19:41 ` Michael Albinus
2012-03-22 21:30 ` Lennart Borgman
2012-03-23 7:48 ` Michael Albinus [this message]
2012-03-23 12:36 ` Lennart Borgman
2012-03-23 12:33 ` Christoph Scholtes
2012-03-23 12:40 ` Dani Moncayo
2012-03-23 13:03 ` Dani Moncayo
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=871uojkbag.fsf@gmx.de \
--to=michael.albinus@gmx.de \
--cc=11065@debbugs.gnu.org \
--cc=lennart.borgman@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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).