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 -----------------------------------------------------------------

On 31-7-2010 3:00, Aditya Mahajan wrote:

On Sat, 31 Jul 2010, Hans Hagen wrote:

...

...

[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 have started use \??whatever?? to avoid clashing with Wolfgang :-)

...

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'.

+1

...

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.

Wolfgang taught me how to use them and now I use (http://github.com/adityam/filter/blob/master/t-filter.tex)

\def\externalfilterparameter #1{\csname\docheckparentparameter{\??externalfilter??\currentexternalfilter}#1\endcsname}

\def\docheckparentparameter #1#2{\ifcsname#1#2\endcsname#1#2\else\expandafter\redocheckparentparameter\csname#1\s!parent\endcsname#2\fi}

\def\redocheckparentparameter#1#2{\ifx#1\relax\s!empty\else\docheckparentparameter#1#2\fi}

I am pretty sure this does not cover all the situations that arise in the core.

there is an experimental mult-aux.mkiv file in the beta ----------------------------------------------------------------- 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 -----------------------------------------------------------------

On 2-8-2010 9:09, Wolfgang Schuster wrote:

you forgot the comma before '##2'.

Ok, fixed. I also need to add \detokenized...parameter an maybe more. But at least we have something to discuss (apart from \???? namespaces). 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 -----------------------------------------------------------------

Am 31.07.10 00:50, schrieb Hans Hagen:

...

[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

I changed it now to \dowithnextbox and it works as well, the main purpose of the macro is to insert a symbol between paragraphs but it's true you can't know how other people misuse the function.

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

Done although it has to be \doifmode\v!mkii ;)

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 want to use this module myself to present how to include macros to document a modules source (%M, %D etc.).

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. You mean \installparameterhandler in str-def.mkiv?

The macro is interesting but three arguments are enough because 'framed' part is always the same in the parameter commands. Wolfgang