From: Pablo Rodriguez <oinos@gmx.es>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: defining bug not setting up blank spaces
Date: Tue, 14 Feb 2017 19:17:23 +0100 [thread overview]
Message-ID: <47397410-b7d6-d6e1-10fb-1bd46c73f12b@gmx.es> (raw)
In-Reply-To: <2af7197d-1543-701c-7255-6e9258dbe3fc@wxs.nl>
On 02/14/2017 06:41 PM, Hans Hagen wrote:
>> [...]
>> I don’t understand why \setupblank[ab][big] doesn’t work (with a
>> previous \defineblank[ab]).
>>
>> I mean, for most elements \setupelement is possible after \defineelement.
>>
>> What is different with \setupblank?
>
> Well, you cannot
>
> \definecolor[red][r=1]
>
> \setupcolor[red][r=.5]
>
> either. Adapting a blank this way would also be inefficient because then
> we need to keep carry around more state info and all these relatively
> basic core macro are tuned for efficiency
Many thanks for your reply, Hans.
Is there anything wrong in defining the same blank again?
I need to add special blanks in templates. In some documents, those
blanks will be bigger than in other ones. Is there anything wrong in
redefining in the second documents the blanks I previously defined in
the template?
Many thanks for your help,
Pablo
--
http://www.ousia.tk
___________________________________________________________________________________
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-02-14 18:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-13 20:16 Pablo Rodriguez
2017-02-14 12:13 ` Hans Hagen
2017-02-14 16:27 ` Pablo Rodriguez
2017-02-14 17:41 ` Hans Hagen
2017-02-14 18:17 ` Pablo Rodriguez [this message]
2017-02-14 19: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=47397410-b7d6-d6e1-10fb-1bd46c73f12b@gmx.es \
--to=oinos@gmx.es \
--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).