Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
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:	<20030731035047.31922.qmail@web21409.mail.yahoo.com>
Date:	Wed, 30 Jul 2003 20:50:47 -0700 (PDT)
From:	Rick Rankin <rick_rankin AT yahoo DOT com>
Subject:	Re: "Using Cygwin Effectively with Windows" -- Draft of new User's Guide section
To:	Joshua Daniel Franklin <joshuadfranklin AT yahoo DOT com>, cygwin AT cygwin DOT com
In-Reply-To:	<20030730214151.A8540@ns1.iocc.com>
MIME-Version:	1.0

--- Joshua Daniel Franklin <joshuadfranklin AT yahoo DOT com> wrote:
> On Wed, Jul 30, 2003 at 11:56:15PM +0200, Hannu E K Nevalainen wrote:
> > > From: Joshua Daniel Franklin
> > 
> > > I've thrown together a prospective "Using Cygwin Effectively with
> > > Windows" section for the User's Guide.
> > >
> > > If you'd like to look at it as a web page:
> > > <http://iocc.com/~joshua/tmp/using-effectively.html>
> > 
> > In the next to last paragraph there is a strange thing ;-)
> >  "Therefore these two types of links differently."
> 
> Good catch.  
> 
> > > Some things:
> > --8<--
> > > --Documentation of printing is sparse since I don't really do it much.
> > > Does anyone have extensive documentation of their complex setup?
> > 
> >  I'd say stay basic: i.e. tell that:  (This is quickly sribbled text, take
> > heed!)
>  
> OK, here is the updated section:
> 
> --BEGIN
> There are several options for printing from Cygwin, including the native
> Windows lpr.exe, and the simlple lpr found in cygutils. The cygutils version
> will print to the printer definted in your PRINTER environment variable. It
> also accepts network printer names in backslash notation (\\COMPUTER\Printer
> Share), which must be escaped from shells such as bash (\\\\COMPUTER\\Printer
> Share). If you have a command in a script such that it may be processed twice
> by the shell, you may need to double-escape the name
> (\\\\\\\\COMPUTER\\\\Printer Share). Note that lpr does no conversion of
> data; the printer must recognize the format of the data that is sent to it.
> Failing to do so will make the printer do random things, hang, or ignore the
> input. If your printer supports PostScript, packages such as a2ps and
> enscript can prepare text files for printing. The ghostscript package also
> provides some translation from PostScript to various native printer
> languages.
> --END
> 
Umm, the current version of lpr accepts forward slashes (//COMPUTER/Printer)
now, as well. No need to fool with all the escaping.

--Rick

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -