This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Re: Printing under Cygwin on W2K
- From: Igor Pechtchanski <pechtcha at cs dot nyu dot edu>
- To: Chris Carlson <ccarlson at istor dot com>
- Cc: cygwin at cygwin dot com
- Date: Thu, 3 Jun 2004 13:39:03 -0400 (EDT)
- Subject: Re: Printing under Cygwin on W2K
- References: <7D036BD3216A084DB1BD9D62BCEAF29049A414@mail1irv.inside.istor.com>
- Reply-to: cygwin at cygwin dot com
On Thu, 3 Jun 2004, Chris Carlson wrote:
> According to the documentation, the following should print on the
> default printer:
>
> bash$ cat myfile.txt > PRN
>
> What I find is that a new file is created named "PRN".
Known problem. There's a patch pending for this -- once it's checked in,
this functionality should be available again. Until then, use lpr from
the cygutils package...
> Also according to the documentation, cygwin understands the double-slash
> form used in Windows. Thus the following should work:
>
> bash$ cat myfile.txt > //Dc1irv/laser1
>
> This returns:
>
> bash: //Dc1irv/laser1: No such host or network path
Nope, that shouldn't work. I don't think you can redirect output to a
printer name even from the Windows console, much less from Cygwin. In
any case, Cygwin doesn't treat printer shares as devices.
> So, what is the proper method for printing under cygwin?
Either "lpr" or, if you want to get fancier, "a2ps" or "enscript".
Igor
> BTW: uname -a returns:
>
> CYGWIN_NT-5.0 jackal 1.5.10(0.116/4/2) 2004-05-25 22:07 i686 unknown
> unknown Cygwin
>
> Thanks in advance.
>
> Chris Carlson
> iStor Networks, Inc.
--
http://cs.nyu.edu/~pechtcha/
|\ _,,,---,,_ pechtcha@cs.nyu.edu
ZZZzz /,`.-'`' -. ;-;;,_ igor@watson.ibm.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/