[NTG-context] Overriding / redefining / disabling standard commands

Wolfgang Schuster schuster.wolfgang at gmail.com
Mon Jun 25 23:52:59 CEST 2018


> Rik Kabel <mailto:context at rik.users.panix.com>
> 25. Juni 2018 um 22:49
> List,
>
> What is the preferred way to override a standard command?
>
> My use case is that I am trying to produce html (and epub, but that 
> has a long long way to go) from the same source I use for pdf. Some 
> features are not needed, and I have separate environment files for 
> each output format to accommodate the differences.
>
> I would like to override the standard \index command in one of those 
> environment files, eliminating the generation of index references. 
> There may be other constructs as well that would benefit from this 
> simplification while allowing a common content source file.

You can use the “*export” mode to disable commands when the export is 
enabled.

\startmode[ebook]
\setupbackend[export=yes]
\stopmode

\starttext

\index{Knuth}\input knuth

\index{Ward}\input ward

\index{Zapf}\input zapf

\startnotmode[*export]
\completeregister[index]
\stopnotmode

\stoptext

Wolfgang
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.ntg.nl/pipermail/ntg-context/attachments/20180625/11756eb2/attachment.html>


More information about the ntg-context mailing list