From: siep.kroonenberg@wkap.nl
Subject: Re: Fwd: Re: beginner's questions
Date: Tue, 14 Nov 2000 09:49:58 +0100 (CET) [thread overview]
Message-ID: <01JWIY7DIIHEAM3VNO@wkap.nl> (raw)
On 14 Nov, Berend de Boer wrote:
> siepo@cybercomm.nl wrote:
>
>> I think I would like Context a lot better if there was less of that
>> hard-coded functionality. It is better to spend 10 minutes writing a
>> line or two of code than to search for hours for something that may or
>> may not be there, and, with my luck, probably isn't.
>
> Well, I agree I had to spend some time adapting to ConTeXt, but in
> general the good index, list of macro's and grep have been my friends.
>
> I'm not really a hard-core TeX programmer myself, so it would take me at
> least as long to lookup things in the TeX book than in the ConTeXt
> manual.
>
> I think what you need is some kind of HOW-TO document. Couldn't you
> create an initial list, things you have found hard or impossible to do
> with ConTeXt? In that document we can answer things about fine-tuning,
> or making ConTeXt do things it does quite hard to prevent you to do :-)
>
> Groetjes,
>
> Berend. (-:
I don't need a HOW-TO. I need a formal description of commands and
parameters. I asked for this on this list but nobody volunteered.
What I tried to do at that occasion was creating a non-indenting list
structure. This turned out to require a new hack of Hans, which turned
out to contain a bug with vertical spacing for nested lists. Also, I
failed to turn justification back on. Then I gave up using lists for
this particular case.
--
Siep Kroonenberg
Kluwer Academic Publishers, Prepress Department
Achterom 119, 3311 KB Dordrecht, The Netherlands
siep.kroonenberg@wkap.nl
next prev reply other threads:[~2000-11-14 8:49 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200011131338.OAA13198@plane.elvenkind.com>
2000-11-13 21:26 ` siepo
2000-11-13 23:05 ` Frans Goddijn
2000-11-14 8:17 ` Hans Hagen
2000-11-14 6:30 ` Berend de Boer
2000-11-14 8:49 ` siep.kroonenberg [this message]
2000-11-14 10:21 ` Hans Hagen
2000-11-15 14:35 ` siep.kroonenberg
2000-11-15 14:55 ` Hans Hagen
2000-11-14 8:08 ` Hans Hagen
2000-11-14 8:40 siep.kroonenberg
2000-11-14 9:32 ` Frans Goddijn
2000-11-14 10:45 ` Hans Hagen
2000-11-14 12:36 ` Frans Goddijn
2000-11-14 13:28 ` Hans Hagen
2000-11-14 14:16 ` Frans Goddijn
2000-11-14 14:30 ` Hans Hagen
2000-11-14 15:14 ` Frans Goddijn
[not found] ` <3A125000.C8291841@earthlink.net>
2000-11-15 15:19 ` Frans Goddijn
2000-11-14 12:53 ` Frans Goddijn
2000-11-14 13:04 ` Berend de Boer
2000-11-21 15:50 siep.kroonenberg
2000-11-21 18:31 ` Frans Goddijn
2000-11-22 8:42 siep.kroonenberg
2000-11-22 9:50 ` Frans Goddijn
2000-11-22 11:12 ` Hraban
2000-11-22 15:56 ` Hans Hagen
2000-11-22 16:16 ` Hraban
2000-11-22 16:39 ` Hans Hagen
2000-11-22 16:58 ` Hraban
2000-11-22 17:38 ` Hans Hagen
2000-11-23 17:12 ` Hraban
2000-11-22 18:28 ` Berend de Boer
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=01JWIY7DIIHEAM3VNO@wkap.nl \
--to=siep.kroonenberg@wkap.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).