Mailing-List:	contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT sources DOT redhat DOT com>
List-Help:	<mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-owner AT sources DOT redhat DOT com
Delivered-To:	mailing list cygwin AT sources DOT redhat DOT com
To:	Keith Amidon <camalot AT picnicpark DOT org>
Cc:	"rcp.el mailing list" <emacs-rcp AT amaunet DOT cs DOT uni-dortmund DOT de>,
	ntemacs-users AT cs DOT washington DOT edu, cygwin AT cygwin DOT com
Subject:	Re: tramp on NT emacs
References:	<87u24cunip DOT fsf AT mah DOT mcdermott DOT com>
	<864rvfipjf DOT fsf AT camalot DOT picnicpark DOT org>
From:	mah AT everybody DOT org (Mark A. Hershberger)
X-URL:	http://mah.everybody.org/
Date:	23 Apr 2001 12:48:41 -0500
In-Reply-To:	<864rvfipjf.fsf@camalot.picnicpark.org>
Message-ID:	<877l0btsli.fsf@mah.mcdermott.com>
Lines:	40
User-Agent:	Gnus/5.0808 (Gnus v5.8.8) Emacs/21.0.102
MIME-Version:	1.0

Keith Amidon <camalot AT picnicpark DOT org> writes:

> Inspired by Mark, I've been poking around trying to get tramp working
> on nt-emacs 20.7 with the Cygwin ssh port.  I'm really
> close. Hopefully someone knows what needs to be done to take this the
> rest of the way.

I've got a quick synopsis of what I've done to attempt to get
tramp working up at <http://mah.everybody.org/docs/tramp-on-nt>.

Though I don't say so on that page, I'm getting the following
in my *Messages* buffer:

    Couldn't find exit status of `ls -d "/home/mah/.bash_profile"'

when I try find-file on /tr AT su:mah AT mah:/home/mah/.bash_profile.

Looking through the debug buffer, it seems to be coming from the
following two lines:

    ls: tramp_exit_status 1
    / this file does not exist : No such file or directory

The results of the two commands in

    ls "/ this file does not exist"; echo tramp_exit_status $?

are being interpolated.

So, now I need some way to ensure that STDERR and STDOUT will
wait on each other.  Looking over the bash manpage, I can't see
any way to coerce it.

Ahhh... That's about it for me.  Anyone else?

Mark.

-- 
		      ommnes exeunt in mysterium
		     All Things Lead into Mystery

--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple

- Raw text -