[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: tramp (2.1.16-pre); backtrace for windows connection problem

From: Dave Abrahams
Subject: Re: tramp (2.1.16-pre); backtrace for windows connection problem
Date: Tue, 1 Feb 2011 11:55:05 -0500

Hallelujah!  Adding an extra space after $\ also fixes it, so we can
work around this problem in tramp.  Not sure whether this should be
considered a bug in shell-quote-argument or not, ultimately.

On Tue, Feb 1, 2011 at 11:47 AM, Dave Abrahams <address@hidden> wrote:
> On Tue, Feb 1, 2011 at 11:33 AM, Michael Albinus <address@hidden> wrote:
>> Dave Abrahams <address@hidden> writes:
>>> The 2nd command yields this prompt:
>>>   $  PS2=
>> That's the problem. Tramp expects "$ " as prompt in this case. Somehow,
>> your shell on the remote system does not like a command like
>> # exec env ENV='' PROMPT_COMMAND='' PS1=\$\  PS2='' PS3='' /bin/sh
> Yeah, but using quotes instead of backslashes fixes it
>> Which shell do you run after login?
> This is cygwin bash, but IIRC I had the same problem with msys bash.
> Connection doesn't work at all if I just run the windows shell.
> --
> Dave Abrahams
> BoostPro Computing

Dave Abrahams
BoostPro Computing

reply via email to

[Prev in Thread] Current Thread [Next in Thread]