Mail Archives: cygwin/2003/07/30/22:57:49
On Wed, 30 Jul 2003, Joshua Daniel Franklin 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
We-ell, this is not quite true... The lpr from cygutils will accept
*Windows* printer names (either local, or remote). The UNC (backslash)
notation may be used for remote printers. The printer name may need to be
escaped if it contains spaces or backslashes (by either adding backslashes
or using single quotes).
> 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
You may also want to mention that some (most?) printers support printing
text files, so lpr should just magically work on plain text...
> 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.
IIRC, gsprint is actually not part of the Cygwin ghostscript package, but
the Windows version of Ghostscript or Ghostview...
HTH,
Igor
> --END
>
> > Hannu E K Nevalainen (garbage mail) wrote:
>
> By the way, why not just set your reply address to cygwin AT cygwin instead
> of the garbage? (Unless your real address *is* garbage_collector AT telia.)
--
http://cs.nyu.edu/~pechtcha/
|\ _,,,---,,_ pechtcha AT cs DOT nyu DOT edu
ZZZzz /,`.-'`' -. ;-;;,_ igor AT watson DOT ibm DOT com
|,4- ) )-,_. ,\ ( `'-' Igor Pechtchanski, Ph.D.
'---''(_/--' `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-. Meow!
"I have since come to realize that being between your mentor and his route
to the bathroom is a major career booster." -- Patrick Naughton
--
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 -