From: Akshat Kumar <akumar@mail.nanosouffle.net>
To: 9fans@9fans.net
Subject: Re: [9fans] page(1)
Date: Fri, 20 Feb 2009 17:40:06 -0800 [thread overview]
Message-ID: <150e6de47d386b33e6a4340b7c4fcaa1@mail.nanosouffle.net> (raw)
In-Reply-To: dd6fe68a0902201732i12e4e4d3xf83c5966612dd4a4@mail.gmail.com
[-- Attachment #1: Type: text/plain, Size: 423 bytes --]
No, they don't work in png(1) either:
term% hget http://9grid.es/screens/screen1.png|png
png: loadimage <stdin> of 2430000 bytes failed: loadimage: insufficient data
term% png n/dump/usr/akumar/plan9/screens/nihongonokawa.png
png: loadimage n/dump/usr/akumar/plan9/screens/nihongonokawa.png of 1310720 bytes failed: loadimage: insufficient data
(the latter is a snapshot of /dev/screen taken with topng(1))
ak
[-- Attachment #2: Type: message/rfc822, Size: 3207 bytes --]
From: Russ Cox <rsc@swtch.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] page(1)
Date: Fri, 20 Feb 2009 17:32:52 -0800
Message-ID: <dd6fe68a0902201732i12e4e4d3xf83c5966612dd4a4@mail.gmail.com>
On Fri, Feb 20, 2009 at 5:03 PM, Akshat Kumar
<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.
If they fail in page, do they work in png?
Do you happen to have another program
named "png" in your path before /bin/png?
Russ
next reply other threads:[~2009-02-21 1:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-21 1:40 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:28 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=150e6de47d386b33e6a4340b7c4fcaa1@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).