From: Hans van der Meer <hansm@science.uva.nl>
Subject: Re: strange \v!on
Date: Wed, 25 Jan 2006 21:08:17 +0100 [thread overview]
Message-ID: <057E24B4-28E1-4F8E-8E78-DFF925B6B7FA@science.uva.nl> (raw)
In-Reply-To: <43D75EEB.7000509@elvenkind.com>
Well, obviously I interpreted the use of \V!-macros wrong.
I understood it being the ConTeXt way of making command strings
language independent, as in for example.
\c!corner=\v!rectangular
Using code like this in a setup-getparameters combination.
The article "Context System macros part1" <by the way is er a part @?
> provided the inspiration (example on page 11). Since I am adapting
an old plaintex -> latex macro pack now -> context I thought it handy
to put in that independence, as seems to come for free.
Clearly I am not grasping the real meaning. Will you enlighten me? If
it doesn't takes to much of your time to explain.
On Jan 25, 2006, at 12:20, Taco Hoekwater wrote:
>
> Hans van der Meer wrote:
>> Encountered something strange setting up the parameters of framed.
>>
>> This runs normal: \setupframed[frame=off,strut=\v!no, ...
>> This gives an error: \setupframed[frame=\v!off,strut=\v!no, ...
>> The same happens with \v!on as parameter.
>
> In both cases the use of the \v! prefix is wrong (the strut=\v!no
> will not be obeyed), but only one of the two results in an error,
> because context handles some parameters differently from other
> parameters.
>
> Cheers, Taco
>
yours sincerely,
dr. H. van der Meer
next prev parent reply other threads:[~2006-01-25 20:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-25 11:04 Hans van der Meer
2006-01-25 11:20 ` Taco Hoekwater
2006-01-25 20:08 ` Hans van der Meer [this message]
2006-01-25 21:02 ` Taco Hoekwater
2006-01-25 21:20 ` Hans van der Meer
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=057E24B4-28E1-4F8E-8E78-DFF925B6B7FA@science.uva.nl \
--to=hansm@science.uva.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).