Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Date: Fri, 7 Dec 2001 16:55:24 +0100 From: Corinna Vinschen To: cygwin AT cygwin DOT com Subject: Re: ghostscript binmode weirdness Message-ID: <20011207165524.Q740@cygbert.vinschen.de> Mail-Followup-To: cygwin AT cygwin DOT com References: <4 DOT 3 DOT 1 DOT 2 DOT 20011207092543 DOT 02363bd0 AT pop DOT ma DOT ultranet DOT com> <3C10E38F DOT 4879178D AT research DOT att DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <3C10E38F.4879178D@research.att.com>; from bond@research.att.com on Fri, Dec 07, 2001 at 10:43:11AM -0500 On Fri, Dec 07, 2001 at 10:43:11AM -0500, Gregory W. Bond wrote: > thanks for the reply larry - i realize that fixing the ghostscript port would > be a solution, but my impression from reading the cygwin user manual is that > setting CYGWIN to binmode could serve as a workaround - in my case it didn't > and i don't understand why - i'm beginning to suspect that cygwin is ignoring > that i've set CYGWIN to binmode which would be a cygwin bug That's not what the CYGWIN=binmode setting is for. http://cygwin.com/cygwin-ug-net/using-cygwinenv.html The workaround you're talking about would be to use binary mount points. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Developer mailto:cygwin AT cygwin DOT com Red Hat, Inc. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/