Re: Overriding / redefining / disabling standard commands

[Wolfgang Schuster <schuster.wolfgang@gmail.com>]

[-- Attachment #1.1: Type: text/plain, Size: 1000 bytes --]


> Rik Kabel <mailto:context@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

[-- Attachment #1.2: Type: text/html, Size: 2085 bytes --]

[-- Attachment #2: Type: text/plain, Size: 492 bytes --]

___________________________________________________________________________________
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
___________________________________________________________________________________