From: Hans Hagen <pragma@wxs.nl>
Subject: updates
Date: Tue, 15 Nov 2005 14:32:35 +0100 [thread overview]
Message-ID: <4379E373.1030401@wxs.nl> (raw)
Hi,
The next couple of weeks there will probably more 'updates' than normal;
this is due to the fact that i'm adding long due features and such. I
also want to move on to the ruby variants of texexec and texutil, so i
want the latest versions to be available (for testers).
Currently I'm uploading a version that
- fixes a problem introduced when implementing the \currentvalue hack
(side effect was that the non english interfaces behaved weird)
- a long standing wish of g.b. dealing with indentation (i tried to
provide a more or less robust solution); the following works ok here
(gb/taco: \noindent does not work in such cases, one really needs to
make a handler the last action taken after a stop...; btw, suppressing a
next indendation is best done with \noindentation which is what the auto
thing used deep down)
\setupindenting[small,yes]
\setupitemize [indentnext=auto]
\setuptyping [indentnext=auto]
\setupformulas[indentnext=auto]
\starttext
\input tufte
\startitemize
\item ccc
\stopitemize
\input tufte
\startitemize
\item ccc
\stopitemize
\input tufte
\startitemize
\item ccc
\stopitemize
\page
\input tufte
\starttyping
ccc
\stoptyping
\input tufte
\starttyping
ccc
\stoptyping
\input tufte
\starttyping
ccc
\stoptyping
\page
\input tufte
\startformula
a = b
\stopformula
\input tufte
\startformula
a = b
\stopformula
\input tufte
\startformula
a = b
\stopformula
\stoptext
Hans
next reply other threads:[~2005-11-15 13:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-15 13:32 Hans Hagen [this message]
2005-11-16 9:42 ` updates Alexander Lazic
2005-11-16 10:39 ` updates Hans Hagen
2005-11-16 10:59 ` updates Alexander Lazic
-- strict thread matches above, loose matches on Subject: below --
2004-08-09 19:26 updates Hans Hagen
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=4379E373.1030401@wxs.nl \
--to=pragma@wxs.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).