From: Hans Hagen <j.hagen@xs4all.nl>
To: Rik Kabel <context@rik.users.panix.com>,
"ntg-context@ntg.nl >> mailing list for ConTeXt users"
<ntg-context@ntg.nl>
Subject: Re: Overriding / redefining / disabling standard commands
Date: Tue, 26 Jun 2018 09:35:06 +0200 [thread overview]
Message-ID: <f0eefbd9-87ab-f101-5852-e3fe1eca39fa@xs4all.nl> (raw)
In-Reply-To: <d587c800-7c6a-496d-74ca-aa6c3b177770@rik.users.panix.com>
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 to export when export is off so it would mean
permanently disabled and not locally in a run) ... what commands are we
talking about
Hans
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl
-----------------------------------------------------------------
___________________________________________________________________________________
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
___________________________________________________________________________________
next prev parent reply other threads:[~2018-06-26 7:35 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-25 20:49 Rik Kabel
2018-06-25 21:52 ` Wolfgang Schuster
2018-06-25 23:11 ` Rik
2018-06-26 0:11 ` Alan Braslau
2018-06-26 0:50 ` Rik Kabel
2018-06-26 2:00 ` Alan Braslau
2018-06-26 2:44 ` Rik Kabel
2018-06-26 7:35 ` Hans Hagen [this message]
2018-06-26 12:56 ` Alan Braslau
2018-06-26 13:22 ` Hans Hagen
2018-06-26 6:34 ` Wolfgang Schuster
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=f0eefbd9-87ab-f101-5852-e3fe1eca39fa@xs4all.nl \
--to=j.hagen@xs4all.nl \
--cc=context@rik.users.panix.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).