From: "Idris Samawi Hamid ادريس سماوي حامد" <Idris.Hamid@colostate.edu>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: What is a better way to do this macro?
Date: Fri, 17 Jul 2015 15:01:34 -0600 [thread overview]
Message-ID: <op.x1xrcwifejo439@ishamid-pc> (raw)
In-Reply-To: <55A94461.3070407@gmail.com>
On Fri, 17 Jul 2015 12:07:29 -0600, Wolfgang Schuster
<schuster.wolfgang@gmail.com> wrote:
>> Idris Samawi Hamid ادريس سماوي حامد <mailto:Idris.Hamid@colostate.edu>
>> 17. Juli 2015 19:56
>> On Thu, 16 Jul 2015 22:35:45 -0600, Wolfgang Schuster
>> <schuster.wolfgang@gmail.com> wrote:
>>
>>
>> Works like a charm. Question: Should the wiki page be edited:
>>
>> http://wiki.contextgarden.net/Command/setupframed
>>
>> It has the equivalent of
>>
>> foregroundstyle = <name>
>>
>> Shouldn't that be changed to
>>
>> foregroundstyle = <command>
>>
>> Originally I looked for keys mapped to <command> so I tried bottom and
>> top because and those are the only keys that are mapped to <command>
>> in the description. Or am I missing something here?
>
> The foregroundstyle should list the same arguments as the style key from
> other commands/environments.
>
> For a example look at the arguments for \setupdescriptions:
> http://wiki.contextgarden.net/Command/setupdescriptions
Ah! Perhaps disambiguating would help unsuspecting users. So in
\setupdescriptions we have things like
style = normal bold slanted boldslanted type cap small... command
[i.e. style = <name>|<command>]
color = <name>
before = <command>
So in the explanation of the foregroundstyle key we could have, e.g.
foregroundstyle = <name|command>
making it clear that this key takes both a name and a command argument.
Anyway, thanks kindly and
Best wishes
Idris
--
Idris Samawi Hamid
Professor of Philosophy
Colorado State University
Fort Collins, CO 80523
___________________________________________________________________________________
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
___________________________________________________________________________________
prev parent reply other threads:[~2015-07-17 21:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-16 18:49 Idris Samawi Hamid ادريس سماوي حامد
2015-07-16 19:03 ` Wolfgang Schuster
2015-07-16 19:16 ` Idris Samawi Hamid ادريس سماوي حامد
2015-07-16 20:09 ` Idris Samawi Hamid ادريس سماوي حامد
2015-07-17 4:35 ` Wolfgang Schuster
2015-07-17 17:56 ` Idris Samawi Hamid ادريس سماوي حامد
2015-07-17 18:07 ` Wolfgang Schuster
2015-07-17 21:01 ` Idris Samawi Hamid ادريس سماوي حامد [this message]
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=op.x1xrcwifejo439@ishamid-pc \
--to=idris.hamid@colostate.edu \
--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).