From: "Robert Collins" <robert.collins@itdomain.com.au>
To: "Gregory W. Bond" <bond@research.att.com>, <cygwin@cygwin.com>
Subject: Re: ghostscript binmode weirdness
Date: Sun, 09 Dec 2001 13:45:00 -0000 [thread overview]
Message-ID: <00aa01c180f9$fd40f7f0$0200a8c0@lifelesswks> (raw)
In-Reply-To: <3C13D852.AB52440B@research.att.com>
Send a patch thats contains your fix to the Ghostscript maintainer, cc'd
to cygwin-patches.
Rob
===
----- Original Message -----
From: "Gregory W. Bond" <bond@research.att.com>
To: <cygwin@cygwin.com>
Sent: Monday, December 10, 2001 8:32 AM
Subject: Re: ghostscript binmode weirdness
> ok - i fixed the problem in the ghostscript port - how do i go about
> getting the fix back into the cygwin distro?
>
> p.s. the link you sent me to is very clear about what the
CYGWIN=binmode
> achieves - however, another part of the cywin manual (the one i
happened
> to be reading: http://cygwin.com/cygwin-ug-net/using-textbinary.html)
is
> not nearly so clear which led to my confusion
>
>
> > 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
> >
>
> --
> Gregory W. Bond
> AT&T Labs - Research
> 180 Park Avenue, Rm. D273, Bldg. 103
> P.O. Box 971, Florham Park, NJ, 07932-0971, USA
> tel: (973) 360 7216 fax: (973) 360 8187
>
>
>
> --
> 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/
>
>
--
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/
next prev parent reply other threads:[~2001-12-09 21:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-09 13:40 Gregory W. Bond
2001-12-09 13:45 ` Robert Collins [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-12-06 21:06 Gregory W. Bond
2001-12-07 6:31 ` Larry Hall (RFK Partners, Inc)
2001-12-07 7:55 ` Gregory W. Bond
2001-12-07 8:14 ` Corinna Vinschen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='00aa01c180f9$fd40f7f0$0200a8c0@lifelesswks' \
--to=robert.collins@itdomain.com.au \
--cc=bond@research.att.com \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).