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

On 6/26/2018 9:35 AM, Hans Hagen wrote: On 6/26/2018 4:44 AM, Rik Kabel wrote: I thought that the ability to override a command like \index might be generally useful, and so brought it up to the list when I could not find a way to do it. could be but only when it can be implemented

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

On Tue, 26 Jun 2018 09:35:06 +0200 Hans Hagen wrote: > On 6/26/2018 4:44 AM, Rik Kabel wrote: > > > I thought that the ability to override a command like \index might > > be generally useful, and so brought it up to the list when I could > > not find a way to do it. > could be but only when

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

On 6/26/2018 4:44 AM, Rik Kabel wrote: I thought that the ability to override a command like \index might be generally useful, and so brought it up to the list when I could not find a way to do it. could be but only when it can be implemented efficiently (i don't want to add overhead related

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

Alan Braslau 26. Juni 2018 um 04:00 On Mon, 25 Jun 2018 20:50:51 -0400 \setupregister[index][referencing=off] This option doesn’t exist in MkIV and there is no other option to disable \index. Wolfgang

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

On 6/25/2018 22:00, Alan Braslau wrote: On Mon, 25 Jun 2018 20:50:51 -0400 Rik Kabel wrote: On 6/25/2018 20:11, Alan Braslau wrote: On Mon, 25 Jun 2018 19:11:30 -0400 Rik wrote: On 6/25/2018 17:52, Wolfgang Schuster wrote: \startmode[ebook] \setupbackend[export=yes] \stopmode \starttext

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

On Mon, 25 Jun 2018 20:50:51 -0400 Rik Kabel wrote: > On 6/25/2018 20:11, Alan Braslau wrote: > > On Mon, 25 Jun 2018 19:11:30 -0400 > > Rik wrote: > > > >> On 6/25/2018 17:52, Wolfgang Schuster wrote: > >>> \startmode[ebook] > >>> \setupbackend[export=yes] > >>> \stopmode > >>> > >>>

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

On 6/25/2018 20:11, Alan Braslau wrote: On Mon, 25 Jun 2018 19:11:30 -0400 Rik wrote: On 6/25/2018 17:52, Wolfgang Schuster wrote: \startmode[ebook] \setupbackend[export=yes] \stopmode \starttext \index{Knuth}\input knuth \index{Ward}\input ward \index{Zapf}\input zapf

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

On Mon, 25 Jun 2018 19:11:30 -0400 Rik wrote: > On 6/25/2018 17:52, Wolfgang Schuster wrote: > > \startmode[ebook] > > \setupbackend[export=yes] > > \stopmode > > > > \starttext > > > > \index{Knuth}\input knuth > > > > \index{Ward}\input ward > > > > \index{Zapf}\input zapf > > > >

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

On 6/25/2018 17:52, Wolfgang Schuster wrote: \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 Unfortunately, this does not

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

Rik Kabel 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

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

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