From: Akshat Kumar <akumar@mail.nanosouffle.net>
To: 9fans@9fans.net
Subject: Re: [9fans] page(1)
Date: Fri, 20 Feb 2009 17:28:14 -0800 [thread overview]
Message-ID: <fbcd133dd67fa5c8203d36345bfa3e4b@mail.nanosouffle.net> (raw)
In-Reply-To: e99dc1e9a20b12797e445ebe04f140b7@quanstro.net
[-- Attachment #1: Type: text/plain, Size: 194 bytes --]
Neither works for me.
term% hget http://9grid.es/screens/screen1.png|page
reading through graphics...
warning: couldn't read image: readimage: read count 32400 not 64800: screen id in use
[-- Attachment #2: Type: message/rfc822, Size: 3096 bytes --]
From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] page(1)
Date: Fri, 20 Feb 2009 20:09:13 -0500
Message-ID: <e99dc1e9a20b12797e445ebe04f140b7@quanstro.net>
On Fri Feb 20 20:05:49 EST 2009, akumar@mail.nanosouffle.net wrote:
> Lately, page has been having troubles displaying an increasing number
> of PNG image files. I'm not sure whether this is due to any recent
> changes or what... Even a PNG of /dev/screen taken with topng(1)
> renders just the dreaded question-marks.
>
> Any ideas what's going on here (as a simple test, you can first try
> the screenshot on 9grid.es, which is a PNG, and also isn't rendered
> by page(1) for me, then you can try taking your own snapshot with
> topng(1))?
both of these work for me:
; hget http://9grid.es/screens/screen1.png|page
; hget http://9grid.es/screens/screen1.png|/n/sources/plan9/386/bin/page
- erik
next reply other threads:[~2009-02-21 1:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-21 1:28 Akshat Kumar [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-02-23 20:15 Akshat Kumar
2009-02-23 20:18 ` erik quanstrom
2009-02-24 0:06 ` geoff
2009-02-21 1:49 erik quanstrom
2009-02-21 3:38 ` Federico G. Benavento
2009-02-21 1:40 Akshat Kumar
2009-02-21 1:03 Akshat Kumar
2009-02-21 1:09 ` erik quanstrom
2009-02-21 1:32 ` 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=fbcd133dd67fa5c8203d36345bfa3e4b@mail.nanosouffle.net \
--to=akumar@mail.nanosouffle.net \
--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).