From: Sietse Brouwer <sbbrouwer@gmail.com>
To: Hans Hagen <pragma@wxs.nl>
Cc: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: command reference
Date: Sun, 24 Mar 2013 22:48:17 +0100 [thread overview]
Message-ID: <CAF=dkzyYkGzmz7Wha+EVS-3eTypgmmqHXGgqfLzJZHuPgaFM3A@mail.gmail.com> (raw)
In-Reply-To: <514C9321.7090403@wxs.nl>
Sietse wrote:
>> NB1: I waffled a lot about wiki templates in the previous e-mail, but
>> of course it is also an option to use the Lua tables format and store
>> those files on the wiki. That gives us the visibility and editability
>> of the wiki without binding us to the wiki template format.
Hans wrote:
> isn't wikimedia lua aware nowadays?
Hah, so it is — I didn't know that. That sounds like it might be an
ideal fit at least for displaying the command reference, possibly also
for storing its info. In case anyone else is curious: here are some
useful pages I found. (The information was a bit scattered sometimes,
but this set of pages covers most bases.)
--Sietse
Wikipedia's main page on the Lua extension:
http://en.wikipedia.org/wiki/Wikipedia:Lua
Good example template:
http://en.wikipedia.org/wiki/Module:BananasArgs
The reference manual:
https://www.mediawiki.org/wiki/Extension%3AScribunto/Lua_reference_manual
The extension's page:
http://www.mediawiki.org/wiki/Extension:Scribunto
Some discussion on using Lua databases:
http://lists.wikimedia.org/pipermail/wikitech-l/2013-February/066656.html
___________________________________________________________________________________
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
___________________________________________________________________________________
next prev parent reply other threads:[~2013-03-24 21:48 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-19 18:16 upto current Hans Hagen
2013-03-19 18:47 ` Aditya Mahajan
2013-03-19 19:05 ` Hans Hagen
2013-03-20 1:52 ` Aditya Mahajan
2013-03-20 6:05 ` Otared Kavian
2013-03-20 8:05 ` Meer H. van der
2013-03-20 8:19 ` Keith J. Schultz
2013-03-20 8:40 ` Hans Hagen
2013-03-20 9:27 ` Mojca Miklavec
2013-03-20 9:37 ` Hans Hagen
2013-03-20 8:12 ` Keith J. Schultz
2013-03-20 8:25 ` Marcin Borkowski
2013-03-20 17:54 ` Keith J. Schultz
2013-03-21 10:19 ` Mojca Miklavec
2013-03-21 10:32 ` Alan BRASLAU
2013-03-21 14:26 ` Marcin Borkowski
2013-03-22 7:31 ` Keith J. Schultz
2013-03-22 8:26 ` command reference (was: upto current) Peter Münster
2013-03-22 10:11 ` Procházka Lukáš Ing. - Pontex s. r. o.
2013-03-22 10:25 ` command reference Peter Münster
2013-03-22 12:04 ` Hans Hagen
2013-03-22 14:42 ` command reference (was: upto current) Sietse Brouwer
2013-03-22 16:07 ` Sietse Brouwer
2013-03-22 17:21 ` command reference Hans Hagen
2013-03-24 21:48 ` Sietse Brouwer [this message]
2013-03-25 9:42 ` command reference (was: upto current) Keith J. Schultz
2013-03-25 9:34 ` Keith J. Schultz
2013-03-22 14:19 ` upto current Bill Meahan
2013-03-22 14:32 ` Taco Hoekwater
2013-03-22 14:37 ` luigi scarso
2013-03-22 14:47 ` Hans Hagen
2013-03-25 8:02 ` Keith J. Schultz
2013-03-20 8:49 ` 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='CAF=dkzyYkGzmz7Wha+EVS-3eTypgmmqHXGgqfLzJZHuPgaFM3A@mail.gmail.com' \
--to=sbbrouwer@gmail.com \
--cc=ntg-context@ntg.nl \
--cc=pragma@wxs.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).