From: Wolfgang Schuster <schuster.wolfgang@googlemail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: What’s your favorite command?
Date: Tue, 31 Jan 2012 16:33:35 +0100 [thread overview]
Message-ID: <F7C428D9-74C4-4C97-9956-A41ED129747E@googlemail.com> (raw)
In-Reply-To: <20120131151459.GA20013@phlegethon>
Am 31.01.2012 um 16:15 schrieb Philipp Gesang:
> On 2012-01-30 19:55, Wolfgang Schuster wrote:
>> Hi all,
>>
>> to bring some traffic to the list I have a question where I hope even non regulars send a answer. The ConTeXt package is huge and provides dozen of commands but I guess many have *one* favorite command (maybe also functionality).
>
> Hi Wolfgang & Others,
>
> my favorite feature maybe neither a command nor a macro as such:
> I’m especially fond of one “linguistic” feature that makes
> Context source code easily readable: the (often repeated) “do”
> prefix and “indeed” suffix in macro names. This way the majority
> of macros are to a certain extent self-descriptive, their names
> carrying a hint about the current nesting depth and the number of
> steps already executed before the macro itself is encountered.
> A crude scripted scan of the directory context/tex/texmf-context/tex/context/base/
> reveals the longest prefixed macro name to be
> “\dofinishregisterstructurepageregister”
> (not yet underscorified), and the longest suffixed one
> “\syst_helpers_inspect_next_parenthesis_character_indeed”.
> Finally, the macro
> “\dododododoGTC”
> has the most “do” prefixes of all.
>
> I hereby declare these three my favorite macros, although I never
> read their definitions, let alone used them.
The second is part of the internals for \doifnextparenthesiselse.
> Thanks for the clarity
> Philipp
>
> PS: Anybody fond of “\@EAEAEAEAEAEA”?
The @ is a dying symbol in MkIV because the underscore has replaced it
and there are now alternative names for these function, the one you mention
can now be written as \tripleexpandafter.
Wolfgang
___________________________________________________________________________________
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-01-31 15:33 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-30 18:55 Wolfgang Schuster
2012-01-30 19:08 ` Marco
2012-01-30 23:10 ` Aditya Mahajan
2012-01-31 11:39 ` Marco
2012-01-30 19:12 ` Thomas A. Schmitz
2012-01-30 23:08 ` Hans Hagen
2012-01-30 21:37 ` Otared Kavian
2012-01-30 22:43 ` Steffen Wolfrum
2012-01-30 23:13 ` Aditya Mahajan
2012-01-30 23:23 ` Mojca Miklavec
2012-01-31 8:48 ` Hans Hagen
2012-01-31 9:42 ` Hans Hagen
2012-01-31 5:45 ` Mikael P. Sundqvist
2012-01-31 8:11 ` Mari Voipio
2012-01-31 8:34 ` Alan Braslau
2012-01-31 8:50 ` Hans Hagen
2012-01-31 8:44 ` luigi scarso
2012-01-31 15:15 ` Philipp Gesang
2012-01-31 15:31 ` Hans Hagen
2012-01-31 15:33 ` Wolfgang Schuster [this message]
2012-01-31 16:23 ` Philipp Gesang
2012-01-31 15:38 ` Wolfgang Schuster
2012-01-31 16:45 ` Marco Pessotto
2012-01-31 18:34 ` Christian Neukirchen
[not found] <mailman.2016.1327999702.4232.ntg-context@ntg.nl>
2012-01-31 10:03 ` What?s " S Barmeier
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=F7C428D9-74C4-4C97-9956-A41ED129747E@googlemail.com \
--to=schuster.wolfgang@googlemail.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).