From: Pietro Gagliardi <pietro10@mac.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] page bug
Date: Fri, 26 Oct 2007 14:44:33 -0400 [thread overview]
Message-ID: <987A472B-AD3F-434C-9D21-B99742B2A46C@mac.com> (raw)
In-Reply-To: <20071026170435.GE26970@hermes.my.domain>
page? I've had that problem with proof and man pages - which is why I
use page.
On Oct 26, 2007, at 1:04 PM, Christian Kellermann wrote:
> * erik quanstrom <quanstro@quanstro.net> [071026 19:00]:
>> it's possible for the first page not to render until you go
>> forward one page
>> and back to the first page. this is a new problem introduced with
>> the
>> page cache code.
>>
> This happens every time with every postscript file I open in /sys/
> doc with page
> from Oct 1st 2007:
> --rwxrwxr-x M 3542 sys sys 236255 Oct 1 05:19 /bin/page
>
> Christian
>
> --
> You may use my gpg key for replies:
> pub 1024D/47F79788 2005/02/02 Christian Kellermann (C-Keen)
prev parent reply other threads:[~2007-10-26 18:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-26 16:57 erik quanstrom
2007-10-26 17:04 ` Christian Kellermann
2007-10-26 18:44 ` Pietro Gagliardi [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=987A472B-AD3F-434C-9D21-B99742B2A46C@mac.com \
--to=pietro10@mac.com \
--cc=9fans@cse.psu.edu \
/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).