From: "Russ Cox" <rsc@swtch.com>
To: 9fans@9fans.net
Subject: Re: [9fans] mpictures and ms: text before is gone
Date: Wed, 30 Apr 2008 14:29:01 -0400 [thread overview]
Message-ID: <20080430183143.8D4C61E8C3A@holo.morphisms.net> (raw)
In-Reply-To: <72C3E623-EFBE-4750-A43E-EB0754D894B3@mac.com>
> Probable bug in lp? I did
>
> hget ... | jpg -9 | lp -dstdout -pp9bitpost > ... # this is a school
> project
> hget | lp -dstdout -pjpgpost > ... # when I realized it existed
>
> However, there is one GIF in my project and that didn't cause any
> problems, so it makes me wonder...
It turns out that using -p does in
fact tickle a bug in lp that ignores
the "nohead" setting for -dstdout.
I've submitted a patch.
Until then, you don't need the -p options
anyway. Lp can figure out what kind of
input you're giving it.
Russ
prev parent reply other threads:[~2008-04-30 18:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-26 22:34 Pietro Gagliardi
2008-04-27 16:43 ` Russ Cox
2008-04-27 20:54 ` Pietro Gagliardi
2008-04-28 8:32 ` Russ Cox
2008-04-28 10:14 ` Pietro Gagliardi
2008-04-30 18:29 ` Russ Cox [this message]
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=20080430183143.8D4C61E8C3A@holo.morphisms.net \
--to=rsc@swtch.com \
--cc=9fans@9fans.net \
/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 NNTP newsgroup(s).