ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <pragma@wxs.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Multicolumn itemizations - again...
Date: Thu, 06 Nov 2008 09:40:07 +0100	[thread overview]
Message-ID: <4912AD67.5070804@wxs.nl> (raw)
In-Reply-To: <20081105203929.GW2264@atos.labs.wmid.amu.edu.pl>

Marcin Borkowski wrote:
> Dnia Wed, Nov 05, 2008 at 09:09:06PM +0100, Marcin Borkowski napisa&#322;(a):
>> Hi,
>>
>> I have
>>
>> \setupitemize[2][a,paragraph,intro,columns,two][stopper=)]
>>
>> in the environment.  In one place, however, I want to have a one-column
>> itemization.  What do I do?  I thought that
>>
>> \startitemize[columns,one]
>>
>> would override the environment setting - but it didn't work.
>>
>> I tried to do something like this:
>>
>> \defineitemgroup[onecolumnitemize]
>> \setuponecolumnitemize[2][a,paragraph,intro][stopper=)]
>>
>> but it didn't work - still the settings from \setupitemize[2][...] were
>> in use.
>>
>> What's going on?
> 
> Before anyone asks me for an example, here it is:
> http://wiki.contextgarden.net/User:Mbork
> (the last part)

concerning the intro ... mixed one-two column modes are somewhat tricky 
and have limitations (if only because tex itself has no concept of 
columns); when mkiv is further down the road i'll look into multi 
columns and see if i can provide more control, but for that i need to 
implement a few other things first

nested itemizations are currently not possible (or more precisely: they 
are (they are intercepted simply because there is no guarantee that all 
varianst work); however you can say \startitemize[n=1] at the second 
level and get just one column then



-----------------------------------------------------------------
                                           Hans Hagen | PRAGMA ADE
               Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
      tel: 038 477 53 69 | fax: 038 477 53 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  : https://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________


  reply	other threads:[~2008-11-06  8:40 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-05 20:09 Marcin Borkowski
2008-11-05 20:39 ` Marcin Borkowski
2008-11-06  8:40   ` Hans Hagen [this message]
2008-11-06  9:04     ` Marcin Borkowski
2008-11-06 12:29       ` Hans Hagen
2008-11-06 16:24         ` Marcin Borkowski
2008-11-06 16:43           ` Wolfgang Schuster
2008-11-06 19:12             ` Marcin Borkowski
2008-11-06 19:00           ` 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=4912AD67.5070804@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).