Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Date: Tue, 21 Jun 2005 11:37:43 +0200
From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: enscript ... > $PRINTER fails
Message-ID: <20050621093743.GB21869@calimero.vinschen.de>
Reply-To: cygwin@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
References: <12AE52872B5C5348BE5CF47C707FF53A5FB85C@rhosvr02.rhotrading.com> <42B7D9F4.8010604@familiehaase.de>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <42B7D9F4.8010604@familiehaase.de>
User-Agent: Mutt/1.4.2i

On Jun 21 11:12, Gerrit P. Haase wrote:
> davidr@rhotrading.com wrote:
> 
> >Up to last week, I was able to do
> >
> >
> >>enscript -p- file.txt > $PRINTER
> >
> >
> >where I had
> >
> >export PRINTER="//rhosvr01/rhohp4100"
> >in my /etc/profile
> >
> >and this worked well.
> >
> >After my hard drive failed and I reinstalled windows, etc.,
> >the above enscript command fails with:
> 
> So you have a different (newer) version of Cygwin installed now?
> Or was the installation before the crash up to date?
> 
> Anyway, please attach the output of cygcheck -svr in your reply.

Didn't we screw that up again in 1.5.17?  AFAICS, this is solved
in CVS and recent snapshots, see http://cygwin.com/snapshots/


Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader          mailto:cygwin@cygwin.com
Red Hat, Inc.

--
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/