From: Rick Crawford <rick@vroop.com>
To: <gentoo-dev@gentoo.org>
Subject: [gentoo-dev] Desktop Configuration Guide Comment
Date: Tue, 23 Jul 2002 15:43:01 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.33.0207231537430.20370-100000@redfort.vroop.com> (raw)
Hello Gentoo Dev folks,
Me and my shiny new Gentoo install thank you for your
documentation/tutorial on achieving desktop nirvana.
One thing that might improve the "Printing" section:
You might note that after emerging gimp-print-cups, it may be necessary
to re-emerge ghostscipt (something I had to do, and others in the forums
have commented on). If this had been in the desktop guide to begin with
I would have saved myself several hours of googling and scratching my
head.
thanks again,
-Rick
reply other threads:[~2002-07-23 18:49 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=Pine.LNX.4.33.0207231537430.20370-100000@redfort.vroop.com \
--to=rick@vroop.com \
--cc=gentoo-dev@gentoo.org \
/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