From: Aditya Mahajan <adityam@umich.edu>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: framed items
Date: Mon, 16 Nov 2009 04:17:27 -0500 (EST) [thread overview]
Message-ID: <alpine.LNX.2.01.0911160416450.19635@ybpnyubfg.ybpnyqbznva> (raw)
In-Reply-To: <fe8d59da0911160114s3a89b8afwe382e2deec205e7@mail.gmail.com>
On Mon, 16 Nov 2009, luigi scarso wrote:
> On Mon, Nov 16, 2009 at 10:12 AM, Aditya Mahajan <adityam@umich.edu> wrote:
>> On Mon, 16 Nov 2009, Wolfgang Schuster wrote:
>>
>>>
>>> Am 16.11.2009 um 09:41 schrieb Thomas A. Schmitz:
>>>
>>>>
>>>> On Nov 16, 2009, at 9:33 AM, Aditya Mahajan wrote:
>>>>
>>>>>> The problem is the vertical alignment of the item number, which should
>>>>>> be at the top of the frame. Is this possible?
>>>>>
>>>>> Add location=top to \setupframed.
>>>>>
>>>>> Aditya
>>>>
>>>> Oh, that's good, thanks Aditya! The baselines still don't quite agree,
>>>> but it's just a minor difference.
>>>
>>> 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)
>>
>> Shoudn't width=broad just work? It doesn't, so I consider this a bug.
> I don't remember :
> is broad related to \hsize or \textwidth ?
I always thought that broad should use as much space as possible. So,
anything more or less is a bug :)
Aditya
___________________________________________________________________________________
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:17 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
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 [this message]
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=alpine.LNX.2.01.0911160416450.19635@ybpnyubfg.ybpnyqbznva \
--to=adityam@umich.edu \
--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).