From: Lars Magne Ingebrigtsen <larsi@ifi.uio.no>
Subject: Screenshots for the manual
Date: 08 Jun 1997 04:45:52 +0200 [thread overview]
Message-ID: <m2lo4lerrz.fsf@proletcult.slip.ifi.uio.no> (raw)
I think I should put some screenshots of each buffer in the manual,
with lots of arrows pointing out what the various elements are.
Sounds cute, eh? I could also include some of the screenshots people
have made when using various customizations (with Mule and smileys and
stuff). And I should put in the toolbar icons in the margins where
the relevant commands are being talked about.
Which brings me to the size issue. Is having a somewhat huge PS file
to print out a real impediment? The current one is 20Mb, but that's
just because I was lazy. It can be wheedled down to ~8Mb by fiddling
a bit. But I would imagine that the size of the "real" manual with
oodles of graphics would indeed be something in the 20-30Mb
neighborhood...
--
(domestic pets only, the antidote for overdose, milk.)
larsi@ifi.uio.no * Lars Magne Ingebrigtsen
reply other threads:[~1997-06-08 2:45 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=m2lo4lerrz.fsf@proletcult.slip.ifi.uio.no \
--to=larsi@ifi.uio.no \
/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).