From: "Gerben Wierda" <Gerben.Wierda@rna.nl>
Subject: Re: Re: Learning ConTeXt, typical hurdle
Date: Mon, 14 Mar 2005 11:28:20 +0100 (CET) [thread overview]
Message-ID: <19934.159.46.248.233.1110796100.squirrel@159.46.248.233> (raw)
In-Reply-To: <42354C36.40807@wxs.nl>
> Gerben Wierda wrote:
>
>> Apart from adapting, the \startitemize \stopitemize does not require me
>> to have a \par at the end. That is also confusing.
>
> That's because it's a different construct (less variants in visualization
> and
> such);
I understand that, but for someone new to ConTeXt, the behaviour of
\whatever after a \definewhatever is unexpected. Especially so if one is
used to LaTeX.
The same is true for the non-implied start of a new column in \startable
after a new row has been declared.
My experience so far with ConTeXt is that it is probably possible to do
all the things I want to do (though I still have a couple of open issues,
see other posts) and I still have the feeling it is very powerful (I
already had that when I first read the manual years ago). But the error
messages I get or the behaviour I see when I make my beginner mistakes are
less illuminating than the LaTeX parts and the behaviour is also not
always friendly (e.g. the \NC needed after a new row in \starttable) or
intuitive or the same across diffferent parts of ConTeXt (\startitemize
versus \startwhatever). And it sometimes very difficult to find
documentation (directory structure, \starttable).
G
next prev parent reply other threads:[~2005-03-14 10:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-10 13:34 Gerben Wierda
2005-03-10 15:06 ` Patrick Gundlach
2005-03-10 16:09 ` Gerben Wierda
2005-03-10 17:05 ` Patrick Gundlach
2005-03-13 22:27 ` h h extern
2005-03-14 6:44 ` Gerben Wierda
2005-03-14 8:32 ` Hans Hagen
2005-03-14 10:28 ` Gerben Wierda [this message]
2005-03-10 17:52 ` Willi Egger
2005-03-13 21:42 ` h h extern
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=19934.159.46.248.233.1110796100.squirrel@159.46.248.233 \
--to=gerben.wierda@rna.nl \
--cc=ntg-context@ntg.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).