From: Hans Hagen <pragma@wxs.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: no indent after blank
Date: Sat, 31 Jul 2010 00:50:37 +0200 [thread overview]
Message-ID: <4C53573D.3060207@wxs.nl> (raw)
In-Reply-To: <4C533C4E.4060705@googlemail.com>
Hi Wolfgang,
> Am 30.07.10 18:37, schrieb Henning Hraban Ramm:
>> (latest beta MkIV)
>>
>> With
>> \setupindenting[yes, medium]
>> there shouldn't be an indent after a \blank IMO.
>>
>> How can I suppress it?
> \setupindenting[yes,medium]
> \starttext
> \input knuth
> \blank
> \noindentation\input ward
> \stoptext
>
> or you use my fancybreak [1] module:
>
> \usemodule[fancybreak]
> \setupindenting[yes,medium]
> \setupfancybreak[indentnext=no]
> \starttext
> \input knuth
> \fancybreak
> \input ward
> \stoptext
>
> [1] http://bitbucket.org/wolfs/fancybreak/src
I'll have a more detailed look at it later (remind me that we need to
formalize this \???? namespace for modules issue; we might need \??? for
the core soon as we run out of \??'s).
I wonder what the side effects of \everyvbox are as the next box content
can have vboxes itself (ok, you can do an everyvbox\emptytoks inside the
\everyvbox); maybe \dowithnextboxcontent can be used here
\def\dodofancybreak
{\begingroup
\everyvbox
{\setupalign[\fancybreakparameter\c!align]%
\doifmode\s!mkiv{\dosetfancybreakattributes\c!style\c!color}}%
\dowithnextbox
{\blank[\fancybreakparameter\c!spacebefore]%
\flushnextbox
\blank[\fancybreakparameter\c!spaceafter]%
\checknextindentation[\fancybreakparameter\c!indentnext]%
\dorechecknextindentation
\endgroup}
\normalvbox}
so:
\dowithnextboxcontent
{\setupalign[\fancybreakparameter\c!align]%
\doifmode\s!mkiv{\dosetfancybreakattributes\c!style\c!color}}%
{\blank[\fancybreakparameter\c!spacebefore]%
\flushnextbox
Another convention could be
\doifmode\s!mkiv{\let\dosetfancybreakattributes\gobbletwoarguments}
so that you then get (less testing):
\dowithnextboxcontent
{\setupalign[\fancybreakparameter\c!align]%
\dosetfancybreakattributes\c!style\c!color}%
{\blank[\fancybreakparameter\c!spacebefore]%
\flushnextbox
As you write nice and clean modules that are perfect examples for
others, we should take some time at the context conference and see if we
can derive some 'module writing conventions'.
I wonder if I should finaly make a definer for \fancybreakparameter like
cases. I had one once but it looked quite horrible and there are subtle
differences between all cases but I'll give it a try some day soon.
Hans
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com
| www.pragma-pod.nl
-----------------------------------------------------------------
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://tex.aanhet.net
archive : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2010-07-30 22:50 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-30 16:37 Henning Hraban Ramm
2010-07-30 20:55 ` Wolfgang Schuster
2010-07-30 21:08 ` Henning Hraban Ramm
2010-07-30 22:50 ` Hans Hagen [this message]
2010-07-31 1:00 ` Aditya Mahajan
2010-08-02 14:41 ` Hans Hagen
2010-08-02 19:09 ` Wolfgang Schuster
2010-08-03 0:17 ` Hans Hagen
2010-08-03 10:41 ` Wolfgang Schuster
2010-07-31 8:01 ` Wolfgang Schuster
2010-07-31 8:33 ` 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=4C53573D.3060207@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).