delorie.com/archives/browse.cgi | search |
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 |
X-Face: | 6=pZ4hVbjN:C?j1$h/-bi4:F%*~B#Rxb$[0%!{5NK"dE:_QRAM]Dzl=$yMu%Rh4xCSm/#>! |
$n%@SHJ](K<taDos\M;zw#b7gIc01F@'f{.guD~];wV{#\SX0YlGR6fREpYY>FJKL,uF\=G=bRJQC$ | |
?+Dlxu*pj.Z,-GK<~y7sd/l*PN\]>}<oCe5vw:p#\Gsv#E(:`3Jl2*()0,/H | |
To: | mah AT everybody DOT org (Mark A. Hershberger) |
Cc: | Keith Amidon <camalot AT picnicpark DOT org>, |
"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> | |
<877l0btsli DOT fsf AT mah DOT mcdermott DOT com> | |
From: | Kai DOT Grossjohann AT CS DOT Uni-Dortmund DOT DE (Kai =?iso-8859-1?q?Gro=DFjohann?=) |
Date: | 23 Apr 2001 19:59:04 +0200 |
In-Reply-To: | <877l0btsli.fsf@mah.mcdermott.com> (mah@everybody.org's message of "23 Apr 2001 12:48:41 -0500") |
Message-ID: | <vaf66fv1orb.fsf@lucy.cs.uni-dortmund.de> |
Lines: | 37 |
User-Agent: | Gnus/5.090003 (Oort Gnus v0.03) Emacs/21.0.103 |
MIME-Version: | 1.0 |
On 23 Apr 2001, Mark A. Hershberger wrote: > 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. Oh, no! What can we do? I'm pretty sure I stopped using 2>/dev/null at some point, and for a reason. I think the problem was that ksh on AIX barfs when encountering 2>/dev/null on a shell builtin. Ah, yes, here's the log entry: /---- | revision 1.312 | date: 2000/05/12 21:04:20; author: grossjoh; state: Exp; lines: +19 -4 | Don't use "set +o history 1>/dev/null 2>/dev/null". AIX chokes on | redirecting stderr here?! \---- Isn't that nice? So. Can we be sure that `ls' is never a shell builtin, and that doing "2>/dev/null" on those commands never fails? I think we cannot be sure. (And also, the exit status of `cd' is sometimes queried, and that's always a shell builtin.) Does anybody have a suggestion? kai -- The passive voice should never be used. -- Want to unsubscribe from this list? Check out: http://cygwin.com/ml/#unsubscribe-simple
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |