From: "Gerrit P. Haase" <gp@familiehaase.de>
To: "Ma, Xiangjiang" <Xiangjiang.Ma@broadvision.com>
Cc: cygwin@cygwin.com
Subject: Re: FW: Can you offer enscript.cfg file for cygwin?
Date: Wed, 17 Apr 2002 23:25:00 -0000 [thread overview]
Message-ID: <111286181657.20020418064429@familiehaase.de> (raw)
In-Reply-To: <46DC955A66CED411B9D3000629A864B602CAB71F@rw-msg-03.broadvision.com>
Hallo Xiangjiang,
> It is better, though I still could not make it print out
> anything
Enscript uses 'lpr' from the cygutils package for printing
to PRN.
Printing under Cygwin was discussed a lot of times on this
list and there is a really good reason why 'lpr' is in the
cygutils package included.
Please search the archives, I'm sorry that I cannot tell you
some more right now, I will have to search the archives too
before I know why you cannot print;)
Gerrit
--
=^..^=
Please keep communication about Cygwin and Cygwin Aplications
on the Cygwin mailinglist.
--
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 parent reply other threads:[~2002-04-18 4:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <46DC955A66CED411B9D3000629A864B602CAB71F@rw-msg-03.broadvision.com>
2002-04-17 23:25 ` Gerrit P. Haase [this message]
2002-04-19 9:41 ` Dave McLaughlin
2002-04-19 11:13 ` lpr problem (was: Re: FW: Can you offer enscript.cfg file for cygwin?) Gerrit P. Haase
2002-04-19 13:03 ` Charles Wilson
2002-04-21 13:28 ` Rick Rankin
2002-04-22 2:16 ` Gerrit P. Haase
2002-04-19 12:54 ` FW: Can you offer enscript.cfg file for cygwin? Charles Wilson
2002-05-02 15:00 ` Dave McLaughlin
2002-04-20 15:38 Ma, Xiangjiang
[not found] <46DC955A66CED411B9D3000629A864B602CAB71D@rw-msg-03.broadvision.com>
2002-04-17 17:02 ` Gerrit P. Haase
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=111286181657.20020418064429@familiehaase.de \
--to=gp@familiehaase.de \
--cc=Xiangjiang.Ma@broadvision.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).