From: Hans Hagen <pragma@wxs.nl>
To: ntg-context@ntg.nl
Subject: Re: two suggestions for \setuphead
Date: Mon, 27 Mar 2017 22:15:51 +0200 [thread overview]
Message-ID: <dc77d453-1fa1-8e57-76d9-00de527fec5b@wxs.nl> (raw)
In-Reply-To: <e42c25f1-5cf3-d64b-5e86-85c908d0ecc7@gmx.es>
On 3/27/2017 9:49 PM, Pablo Rodriguez wrote:
> On 03/27/2017 09:29 PM, Hans Hagen wrote:
>> On 3/27/2017 8:00 PM, Pablo Rodriguez wrote:
>>> Sorry, I was trying to understand why width has no default value in
>>> margin data.
>>
>> because there was no need, as it anchors at the side of the text
>
> Sorry again, but I must be missing something extremely basic.
>
> One of the results of no value for width in margin data is a tricky
> approach to its alignment.
>
> But since I seem to be the only one interested in aligning margin data,
> I guess this is perfectly fine.
Margindata is a general thing, it can be any margin or edge when you
define an instance so you don't know what width is meant. Of course you
can have a parent with some width. Also, margindata can be stacked next
to another one which again can mean a different width. Having no width
set is better than having the wrong one set.
Hans
-----------------------------------------------------------------
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:[~2017-03-27 20:15 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-15 19:59 Pablo Rodriguez
2017-03-22 21:13 ` Hans Hagen
2017-03-23 19:45 ` Pablo Rodriguez
2017-03-26 14:11 ` Hans Hagen
2017-03-26 20:09 ` Pablo Rodriguez
2017-03-26 20:20 ` Wolfgang Schuster
2017-03-26 20:41 ` Pablo Rodriguez
2017-03-27 13:57 ` Pablo Rodriguez
2017-03-27 15:22 ` Hans Hagen
2017-03-27 18:00 ` Pablo Rodriguez
2017-03-27 19:29 ` Hans Hagen
2017-03-27 19:49 ` Pablo Rodriguez
2017-03-27 20:15 ` Hans Hagen [this message]
2017-03-28 17:14 ` Pablo Rodriguez
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=dc77d453-1fa1-8e57-76d9-00de527fec5b@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).