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 Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Message-ID: <20020906172820.76231.qmail@web21008.mail.yahoo.com> Date: Fri, 6 Sep 2002 10:28:20 -0700 (PDT) From: Nicholas Wourms Subject: Re: printing from within Cygwin To: cygwin AT cygwin DOT com In-Reply-To: <20020905054306.A23920@ns.helixdigital.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii --- Dario Alcocer wrote: > On Wed, Sep 04, 2002 at 10:26:36AM -0700, Shankar Unni wrote: > > Igor Pechtchanski wrote: > > > > > Looks like you don't have the mswinpr2 device in your > ghostscript > > > installation... > > > > The GhostScript that comes with Cygwin is built without any of > the > > Windows extensions (the mswin* devices, the Windows console (that > pops > > up if you type "gswin32" in the native Windows distribution), > ...). > > > > I wonder if it's possible to build the Cygwin gs with these > extensions? > > Or at least the Windows devices? There are the "mswindll", > "mswinprn" > > and "mswinpr2" devices, and the "display" device for the Windows > native > > display (the one that "gswin32" pops up). > > Yes, it's definitely doable; it's on my long list of "to-do" items. > As soon as I have more "free time" I'll do it. Please don't do this, I'd rather have gs act like gs does in unix. Having it act like the win32 version defeats the whole purpose. If he wants a win32 version, why doesn't he just use the win32 version. What happens if we get a full lpd which accesses the parallel port via a dev point? I'm sure there are other examples, but again if you want a win32 version go get the win32 version and add it to your PATH. Cheers, Nicholas __________________________________________________ Do You Yahoo!? Yahoo! Finance - Get real-time stock quotes http://finance.yahoo.com -- 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/