From: "Steve Simon" <steve@quintile.net>
To: 9front@9front.org
Subject: Re: [9front] plumb rules for page
Date: Fri, 19 Jan 2018 15:53:07 +0000 [thread overview]
Message-ID: <545680f7b9b9a1e8458f08e51f902574@quintile.net> (raw)
In-Reply-To: <B8686B0C6CDCC532A8172992B102B2AA@sphericalharmony.com>
The effect is useful.
if you plumb multiple images (e.g. from nedmail) then they appear in a single instance
of page as different pages withing page (if you get my meaning). merging multiple
PDFs could get confusing, and having multiple page instances each containing
just one image could be frustrating.
it is non-othogonal but feels ok (to me) in reality.
-Steve
next prev parent reply other threads:[~2018-01-19 15:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-19 4:50 mycroftiv
2018-01-19 15:53 ` Steve Simon [this message]
2018-01-19 16:39 ` [9front] " Stanley Lieber
2018-01-21 14:36 ` Ethan Grammatikidis
2018-01-21 16:28 ` Ethan Grammatikidis
2018-01-19 17:14 mycroftiv
2018-01-20 21:59 ` hiro
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=545680f7b9b9a1e8458f08e51f902574@quintile.net \
--to=steve@quintile.net \
--cc=9front@9front.org \
/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).