From: Hans Hagen <pragma@wxs.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: hsize changes unexpectedly
Date: Sun, 20 Nov 2016 19:37:07 +0100 [thread overview]
Message-ID: <e29efa97-a556-f295-8e74-81907d02ef00@wxs.nl> (raw)
In-Reply-To: <c14bd6c7-26c4-eb9d-c0b0-1910293e9018@panix.com>
On 11/20/2016 6:37 PM, Rik wrote:
> On 2016-11-20 12:16, Wolfgang Schuster wrote:
>>> Rik Kabel <mailto:context@rik.users.panix.com>
>>> 20. November 2016 um 17:49
>>>
>>> Okay.
>>>
>>> What is the scope of local use?
>> It’s used to change the width of a \vbox.
>>
>> \starttext
>>
>> \ruledvbox\bgroup
>> \input ward
>> \egroup
>>
>> \ruledvbox\bgroup
>> \hsize.5\textwidth
>> \input ward
>> \egroup
>>
>> \stoptext
>>
>>> It is different from grouping (as demonstrated by placing the middle
>>> two lines above in braces).
>> Which example?
>>
>> Wolfgang
>
> Sorry, the example at the head of the thread. Originally:
>
> \starttext
>
> \hsize200pt
>
> \dorecurse{60}{\recurselevel: \the\hsize\ \the\textwidth\par}
>
> \stoptext
>
> And with the \hsize in a group :
>
> \starttext
>
> {\hsize200pt
>
> \dorecurse{60}{\recurselevel: \the\hsize\ \the\textwidth\par}}
>
> \stoptext
>
> I did not expect it to change the result, and it does not. So I was
> asking just what Hans meant by “local use.”
when you add stuff to the page it happens globally till (normally) tex
splits off the content that fits to the pagegoal (which is taken from
vsize) .. in principle we could leave hsize untouched but for
consistency and predictability we use textwidth etc .. this has always
been the case
--
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | www.pragma-ade.nl | 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://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2016-11-20 18:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-20 1:47 Rik Kabel
2016-11-20 10:53 ` Hans Hagen
2016-11-20 16:49 ` Rik Kabel
2016-11-20 17:16 ` Wolfgang Schuster
2016-11-20 17:37 ` Rik
2016-11-20 18:37 ` Hans Hagen [this message]
2016-11-20 18:34 ` 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=e29efa97-a556-f295-8e74-81907d02ef00@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).