From: Hans Hagen via ntg-context <ntg-context@ntg.nl>
To: denis.maier@unibe.ch, ntg-context@ntg.nl
Cc: Hans Hagen <j.hagen@xs4all.nl>, oinos@gmx.es
Subject: Re: Wiki: new commands not automatically available for autogenerated syntax (was LTR footnotes from RTL paragraph)
Date: Thu, 13 Jan 2022 09:33:57 +0100 [thread overview]
Message-ID: <a9551b85-5600-3818-4d12-4d8eb6b1714b@xs4all.nl> (raw)
In-Reply-To: <564acdecace74581ae28000a153a9e20@unibe.ch>
On 1/13/2022 6:22 AM, denis.maier@unibe.ch wrote:
> Hi, I wanted to wikify a new command, but I don't fully understand what to do...
>
>> -----Ursprüngliche Nachricht-----
>> Von: Hans Hagen <j.hagen@xs4all.nl>
>> Gesendet: Donnerstag, 13. Januar 2022 00:25
>> An: Maier, Denis Christian (UB) <denis.maier@unibe.ch>; ntg-
>> context@ntg.nl
>> Cc: oinos@gmx.es
>> Betreff: Re: AW: [NTG-context] LTR footnotes from RTL paragraph
>>
> [...]
>>>>
>>>> i'll add this (only a few line addition with no performance hit):
>>>>
>>>> \definealign[MyAlign][r2l,flushleft]
>>>>
>>>> so that you can do
>>>>
>>>> \setupalign[MyAlign]
>>>>
>>>> and you can also use it as value to the align parameter as well ...
>>>> the usual 'context abstraction'
>>>>
>>>> so again something to wikify ...
>>>
>>> Wanted to wikify, but is this already implemented?
>> sure
>
> Ok, so then: Why will creating a page \definealign not create a page with autogenerated syntax? And, the new option for \setupalign does not show up in the autogenerated syntax overview at https://wiki.contextgarden.net/Command/setupalign
>
> I probably don't fully understand how the wiki works in these regards .. can anyone clarify?
when there is a new key or option, wolfgang at some point will add it to
the setups so then it will show up (goes in batches); that is
indepdendent from examples; so when a new key/value is missing, just
signal wolfgang
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
___________________________________________________________________________________
prev parent reply other threads:[~2022-01-13 8:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-13 5:22 Denis Maier via ntg-context
2022-01-13 8:33 ` Hans Hagen via ntg-context [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=a9551b85-5600-3818-4d12-4d8eb6b1714b@xs4all.nl \
--to=ntg-context@ntg.nl \
--cc=denis.maier@unibe.ch \
--cc=j.hagen@xs4all.nl \
--cc=oinos@gmx.es \
/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).