From: siepo@client44-3.kabelA.oprit.rug.nl
Subject: Re: manual
Date: Sat, 12 Aug 2000 14:05:57 +0200 (CEST) [thread overview]
Message-ID: <14741.15781.989852.251473@bitmuis.thuis.nl> (raw)
In-Reply-To: <39952723.740F14A4@pobox.com>
Berend de Boer writes:
>
> > Also some remarks about the manual: since it is intended as reference
> > manual, it should facilitate quick lookup and not require close
> > reading of an entire chapter.
>
> Hmm, I find it served its purpose. But I agree that we can have more
> manuals, one with lots of examples would be nice. Usually I test with a
> small test file or look in the source of the manual is not clear, but
> usually the manual is clear enough. Perhaps you need to get adjusted to
> its style.
>
> Groetjes,
>
> Berend. (-:
Yes, I also write small testfiles when the meaning of the manual is
not clear. But when it is necessary to look at the source then there
is clearly something wrong. Especially since Context has pretensions
to user-friendliness that LaTeX doesn't have.
I suspect that the manual fares better for continuous reading than for
lookup. The suggested typographic changes are intended to make lookup
more efficient.
Siep
next prev parent reply other threads:[~2000-08-12 12:05 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-08-12 10:09 notation, manual siepo
2000-08-12 10:29 ` Berend de Boer
2000-08-12 12:05 ` siepo [this message]
2000-08-12 17:19 ` replies Hraban
2000-08-12 22:29 ` replies Johannes Hüsing
2000-08-16 11:13 ` replies Ed L Cashin
2000-08-16 23:49 ` replies Uwe Koloska
2000-08-17 19:20 ` replies Berend de Boer
2000-08-21 0:51 ` replies Ed L Cashin
2006-03-10 18:29 Manual Jeffrey Drake
2006-03-10 23:32 ` Manual John R. Culleton
2013-04-03 9:57 manual Meer H. van der
2013-04-03 10:06 ` manual Marco Patzer
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=14741.15781.989852.251473@bitmuis.thuis.nl \
--to=siepo@client44-3.kabela.oprit.rug.nl \
--cc=siepo@cybercomm.nl \
/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).