From: Sietse Brouwer <sbbrouwer@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Ctx: list of commands
Date: Mon, 17 Sep 2012 16:20:44 +0200 [thread overview]
Message-ID: <CAF=dkzyi3nYjnBuwdL9R2Anx+Xgb2YrZ6CNNxFZj+M7mQPNU2g@mail.gmail.com> (raw)
In-Reply-To: <20120917155651.143d970a@homerow>
> During the last few months the wiki got plenty of new commands added
> that you could use.
The wiki's list of commands is nowhere near complete, alas. There are
a few (not many) commands *documented* on there that are not
documented elsewhere, but if it's *existence* of commands you want to
know about, the wiki is not a good source, so don't bother.
> But I don't think there's an interface to
> retrieve information from the wiki in an automated fashion.
The API is, in fact, enabled:
http://wiki.contextgarden.net/api.php
But that is more for automated editing than automated retrieval: there
are simply not enough microformats/templates in use to make automated
processing worthwhile.
As for what I myself do when I want to know about the existence or
implementation of commands: I grep the source. This is NOT the same as
producing a list of all commands, of course; just something that is
also very useful, and may often solve the problem.
I've defined a command 'crep' that will automatically search the
source files in the main ConTeXt directory, so if I need something
figure- or footnote-related I'll type
crep '\\def.*figure'
or
crep 'footnote', for example
That will usually at least give me an idea on which file I should look
at. Once inside the file, there are often documenation comments that
start with %D. It's not ideal. But it helps.
## start crep command in my .bashrc and .zshrc
function condir {
cd /opt/context/tex/texmf-context/tex/context/base/
}
# Easy grepping of ConTeXt functions
function crep { condir; grep -R $* * }
## end crep command
Cheers,
Sietse
___________________________________________________________________________________
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:[~2012-09-17 14:20 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-17 13:40 Procházka Lukáš Ing. - Pontex s. r. o.
2012-09-17 13:56 ` Marco Patzer
2012-09-17 14:20 ` Sietse Brouwer [this message]
2012-09-17 15:11 ` Procházka Lukáš Ing. - Pontex s. r. o.
2012-09-17 19:29 ` Philipp Gesang
2012-09-17 22:24 ` Hans Hagen
2012-09-18 9:52 ` output of token.command_name() [was: Ctx: list of commands] Philipp Gesang
2012-09-18 10:25 ` Hans Hagen
2012-09-18 6:44 ` Ctx: list of commands Procházka Lukáš Ing. - Pontex s. r. o.
2012-09-18 7:36 ` Peter Münster
2012-09-18 7:44 ` Procházka Lukáš Ing. - Pontex s. r. o.
2012-09-18 8:28 ` Hans Hagen
2012-09-18 13:49 ` Rogers, Michael K
2012-09-18 14:00 ` Procházka Lukáš Ing. - Pontex s. r. o.
2012-09-18 14:59 ` Hans Hagen
2012-09-18 16:44 ` Sietse Brouwer
2012-09-18 17:52 ` Hans Hagen
2012-09-18 14:58 ` 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=dkzyi3nYjnBuwdL9R2Anx+Xgb2YrZ6CNNxFZj+M7mQPNU2g@mail.gmail.com' \
--to=sbbrouwer@gmail.com \
--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).