ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <pragma@wxs.nl>
Cc: ntg-context@ntg.nl
Subject: Re: more itemization:-)
Date: Mon, 24 Jun 2002 00:49:33 +0200	[thread overview]
Message-ID: <5.1.0.14.1.20020624004432.037db1a8@remote-1> (raw)
In-Reply-To: <87bsa2i1fj.fsf@gundla.ch>

At 03:12 PM 6/23/2002 +0200, Patrick Gundlach wrote:
>Idris S Hamid <ishamid@attbi.com> writes:
>
>Hi,
>
> > One more thing,
> >
> > I need to set some space after the level-3 itemization before the rest 
> of the
> > paragraph. I tried
> >
> > \startitemize[KR][after={\blank[medium]}]
> >
> > but this did not change things.
>
>
>right, because context does not check for this  :)
>
>\unprotect
>\def\stopitemgroup
>   {\iftextitems
>      \removeunwantedspaces\space\ignorespaces
>    \else
>      \par
>    \fi
>    \ifnum\itemcolumndepth=0 \dolistreference \fi % beware !
>    \iffirstlist \else \endgroup \fi % toegevoegd, eerste \som opent groep
>    \ifnum\itemcolumndepth=\itemlevel\relax
>      \stopkolommen
>      \doglobal\newcounter\itemcolumndepth
>      \getitemparameter\itemlevel\c!na
>    \else
>      \ifnum\itemlevel=1                  % !
>        \doitembreak\allowbreak           % !
>      \fi                                 % !
>      \getitemparameter\itemlevel\c!na    % !
>      \doif\@@oospringvolgendein\v!nee\noindentation
>    \fi
>    \endgroup
>    \doglobal\decrement(\itemlevel,\itemincrement)%
>    \egroup}
>\protect
>
>should fix this, but Hans should look over it again, since
>indentnext=yes does not do anything except when you say after=\par,

hm, \endgraf maybe, have to look into that

>which you can't. Why is there a comparison beetween \itemcolumndepth
>and \itemlevel? This code above is really obscure...

well, it's part of the oldest context code ... kind of prehistoric

your patch spoils the packed option; in itemize the before/after keys are 
ignores at level>1

so, fixing this will need a bit more work, like patching the packed handler 
and also the 'before' handling,

so i'll put it on the to do list

for the moment, adding a \blank is the best solution

(or \defineblank[hack][medium]  \blank[hack] so that later you can say 
\defineblank[hack][none])

remind me to fix this

Hans

-------------------------------------------------------------------------
                                   Hans Hagen | PRAGMA ADE | pragma@wxs.nl
                       Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
  tel: +31 (0)38 477 53 69 | fax: +31 (0)38 477 53 74 | www.pragma-ade.com
-------------------------------------------------------------------------
                        information: http://www.pragma-ade.com/roadmap.pdf
                     documentation: http://www.pragma-ade.com/showcase.pdf
-------------------------------------------------------------------------


      parent reply	other threads:[~2002-06-23 22:49 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-21 19:38 Idris S Hamid
2002-06-21 19:52 ` Idris S Hamid
2002-06-23 13:12   ` Patrick Gundlach
2002-06-23 14:24     ` Truncated ouput with m-bib Michael Hallgren
2002-06-23 22:49     ` Hans Hagen [this message]

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=5.1.0.14.1.20020624004432.037db1a8@remote-1 \
    --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).