From: Hans Hagen <pragma@wxs.nl>
To: ntg-context@ntg.nl
Subject: Re: columns
Date: Thu, 03 Oct 2013 18:55:36 +0200 [thread overview]
Message-ID: <524DA188.4000404@wxs.nl> (raw)
In-Reply-To: <134324C0-6A09-4EB5-94BE-E12EF4971041@gmail.com>
On 10/3/2013 12:35 PM, Wolfgang Schuster wrote:
>
> Am 03.10.2013 um 12:26 schrieb H. van der Meer <H.vanderMeer@uva.nl>:
>
>> If I remember well, framedtext sets a localhsize for the width of its content. I guess that is why boxedcolumns stays within the width specified. But is there a specific reason why mixedcolumns in general does not?
>
> The global settings for mixedcolumns are
>
> \setupmixedcolumns
> [maxwidth=\makeupwidth]
>
> which forces columns to use the width of the textblock but boxedcolumns uses this
>
> \definemixedcolumns
> [boxedcolumns]
> [maxwidth=\availablehsize]
>
> where the width of the columns depends on the available width of the environment,
> e.g. in a narrower environment or in a frame the you get shorter columns.
also, boxedcolumns, as the name says, are for use in boxes while by
default mixedcolumns (unless set up as boxed) are operating at the page
level (the so called mvl)
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
-----------------------------------------------------------------
___________________________________________________________________________________
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:[~2013-10-03 16:55 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-03 8:21 columns H. van der Meer
2013-10-03 9:09 ` columns Wolfgang Schuster
2013-10-03 10:02 ` columns H. van der Meer
2013-10-03 10:07 ` columns Wolfgang Schuster
2013-10-03 10:26 ` columns H. van der Meer
2013-10-03 10:35 ` columns Wolfgang Schuster
2013-10-03 16:55 ` Hans Hagen [this message]
2013-10-03 20:12 ` columns luigi scarso
-- strict thread matches above, loose matches on Subject: below --
2007-06-29 16:10 columns Patrick Gundlach
2007-06-29 17:13 ` columns Aditya Mahajan
2007-06-29 17:39 ` columns Patrick Gundlach
2007-06-29 18:37 ` columns Aditya Mahajan
2007-07-03 9:15 ` columns Patrick Gundlach
2003-04-14 19:08 The Context styles library John Culleton
2003-04-14 20:15 ` Patrick Gundlach
2003-04-17 12:06 ` Columns Sytse Knypstra
2003-04-17 12:28 ` Columns Patrick Gundlach
2003-04-17 13:43 ` Columns Sytse Knypstra
2003-04-17 13:54 ` Columns Patrick Gundlach
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=524DA188.4000404@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).