9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Pietro Gagliardi <pietro10@mac.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] mpictures and ms: text before is gone
Date: Mon, 28 Apr 2008 06:14:23 -0400	[thread overview]
Message-ID: <72C3E623-EFBE-4750-A43E-EB0754D894B3@mac.com> (raw)
In-Reply-To: <20080428083512.AE1361E8C4D@holo.morphisms.net>

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

The only postscript I know is the color changing code (which I learned
from your talk slides); this problem confused me.

On Apr 28, 2008, at 4:32 AM, Russ Cox wrote:

>> /n/sources/contrib/pietro/saturn.tar has an example of what I mean.
>>
>> 	troff -ms -mpictures tmac.colors saturnhd.ms history.ms
>
> cpu% tar xf /n/sources/contrib/pietro/saturn.tar
> cpu% for (i in *.ps) echo $i `{sed 1q $i}
> pioneer11.ps %!PS-Adobe-2.0 div 112 page header - research!pg
> saturnsymbol.ps %!PS-Adobe-2.0 div 112 page header - research!pg
> cpu%
>
> Each of these files begins with an lp-style banner page.
> That postscript code reinitializes the postscript interpreter,
> among other things, clearing the page.
>
> Things will work better if you generate the files without
> the banner pages.  Running
>
>  aux/p9bitpost file.bit > file.ps
>
> will produce postscript without the banner page.
>
> I'm quite confused as to how they could have gotten there.
>
> Russ
>
>



  reply	other threads:[~2008-04-28 10:14 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 [this message]
2008-04-30 18:29         ` Russ Cox

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=72C3E623-EFBE-4750-A43E-EB0754D894B3@mac.com \
    --to=pietro10@mac.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).