From: Wolfgang Schuster <schuster.wolfgang@googlemail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: framed items
Date: Mon, 16 Nov 2009 10:16:36 +0100 [thread overview]
Message-ID: <D99542D8-2643-4AEB-B469-4A2B96BCD636@googlemail.com> (raw)
In-Reply-To: <32BF6058-625C-4B52-87E0-5803B45FAEAD@uni-bonn.de>
Am 16.11.2009 um 10:09 schrieb Thomas A. Schmitz:
>
> On Nov 16, 2009, at 9:55 AM, Wolfgang Schuster wrote:
>
>> If you hadn't notice the item is wider then the running text, in MkIV
>> you can say 'width=\dimexpr\textwidth-\itemgrouplistwidth\relax'
>> (not the best method but \localhsize is not available)
>>
>> Wolfgang
>>
>
> Aditya, Wolfgang,
>
> thanks a lot, I now get the visual output I want! So the question remains: any way of making this a hook for startitemize so it gets applied to every \item automatically?
\startitemize[n][command=\framed]
\item {The text of this item is made very long because it is intended to show
the effect of what happens when an item extends to more than just one line.}
\item {This item is relatively short, but also fills more than one line.}
\stopitemize
\startitemize[n][command=\dowithpargument\framed]
\item The text of this item is made very long because it is intended to
show the effect of what happens when an item extends to more than just one
line.
\item This item is relatively short, but also fills more than one
line.
\stopitemize
Wolfgang
___________________________________________________________________________________
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:[~2009-11-16 9:16 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-16 8:21 Thomas A. Schmitz
2009-11-16 8:33 ` Aditya Mahajan
2009-11-16 8:41 ` Thomas A. Schmitz
2009-11-16 8:45 ` Wolfgang Schuster
2009-11-16 8:47 ` Aditya Mahajan
2009-11-16 8:55 ` Wolfgang Schuster
2009-11-16 9:09 ` Thomas A. Schmitz
2009-11-16 9:16 ` Wolfgang Schuster [this message]
2009-11-16 9:26 ` luigi scarso
2009-11-16 9:12 ` Aditya Mahajan
2009-11-16 9:14 ` luigi scarso
2009-11-16 9:17 ` Aditya Mahajan
2009-11-16 9:27 ` luigi scarso
2009-11-16 20:58 ` luigi scarso
2009-11-16 21:29 ` Aditya Mahajan
2009-11-16 21:46 ` luigi scarso
2009-11-16 21:56 ` Wolfgang Schuster
2009-11-16 21:58 ` Aditya Mahajan
2009-11-16 22:20 ` luigi scarso
2009-11-16 22:31 ` luigi scarso
2009-11-16 22:36 ` Wolfgang Schuster
2009-11-16 22:42 ` luigi scarso
2009-11-16 22:49 ` luigi scarso
2009-11-16 23:01 ` Wolfgang Schuster
2009-11-16 23:19 ` luigi scarso
2009-11-16 23:24 ` Wolfgang Schuster
2009-11-17 5:52 ` luigi scarso
2009-11-17 8:12 ` luigi scarso
2009-11-17 8:38 ` Wolfgang Schuster
2009-11-17 15:32 ` Aditya Mahajan
2009-11-17 15:34 ` luigi scarso
2009-11-17 15:41 ` Aditya Mahajan
2009-11-17 23:28 ` luigi scarso
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=D99542D8-2643-4AEB-B469-4A2B96BCD636@googlemail.com \
--to=schuster.wolfgang@googlemail.com \
--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).