Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , 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](KFJKL,uF\=G=bRJQC$ ?+Dlxu*pj.Z,-GK<~y7sd/l*PN\]>} Cc: mah AT everybody DOT org, ntemacs-users AT cs DOT washington DOT edu, Keith Amidon , "rcp.el mailing list" , cygwin AT cygwin DOT com Subject: Re: tramp on NT emacs References: <094EA76FEAA4D411968100508BD8BBF3020F51 AT EQUATOR> From: Kai DOT Grossjohann AT CS DOT Uni-Dortmund DOT DE (Kai =?iso-8859-1?q?Gro=DFjohann?=) Date: 23 Apr 2001 23:11:47 +0200 In-Reply-To: <094EA76FEAA4D411968100508BD8BBF3020F51@EQUATOR> ("Andrew Maguire's message of "Mon, 23 Apr 2001 22:03:08 +0100") Message-ID: Lines: 48 User-Agent: Gnus/5.090003 (Oort Gnus v0.03) Emacs/21.0.103 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii On Mon, 23 Apr 2001, Andrew Maguire wrote: > I have absolutely no idea what you are trying to solve ;-) > but you might like to try: > > set +o history 1>/dev/null 2>&1 > > You may need to do it this way around: > > set +o history 2>&1 1>/dev/null I used to use `set +o history 1>/dev/null 2>&1', actually. The documentation for the shell tells me that this is the right order. (The second order means that stderr goes wherever stdout normally goes, and then stdout is changed to /dev/null. Or something.) But what I used to use didn't work on AIX. The ksh there crashed or something. I don't quite remember. Developing Tramp really teaches me a lot about all the wrinkles of lots of different operating systems. `ls' on SunOS (I think) doesn't return a non-zero exit code when the file unexists, for example... Anyone with an AIX account out there who can try again? Here's the full story: On some systems, I do some_command ; echo tramp_exit_status $? And some_command prints stuff on stderr. So one user is getting this output: tramp_exit_statusSTUFF FROM SOME_COMMAND GOES HERE 42 Of course, the obvious solution is to do this: some_command 2>/dev/null ; echo tramp_exit_status $? But if some_command happens to be a ksh builtin and the whole thing happens to be running on AIX -- boom! Argh. kai -- The passive voice should never be used. -- Want to unsubscribe from this list? Check out: http://cygwin.com/ml/#unsubscribe-simple