From: Nicola <nvitacolonna@gmail.com>
To: ntg-context@ntg.nl
Subject: Re: How to avoid overriding a control sequence?
Date: Mon, 7 Mar 2016 21:30:51 +0100 [thread overview]
Message-ID: <nbkodr$4po$1@ger.gmane.org> (raw)
In-Reply-To: <56DDE1AD.1040302@wxs.nl>
On 2016-03-07 20:16:45 +0000, Hans Hagen said:
> On 3/7/2016 7:40 PM, Nicola wrote:
>> How do I check in ConTeXt whether a control sequence is already
>> defined (to avoid redefining it by accident)?
>>
>> Marginally related to the above, I have tried to use \show, only to
>> discover, to my surprise, that it gives an error. For example:
>>
>> \show\NL
>> \end
>>
>> Does ConTeXt override some of TeX primitives?
>
> yes, like \month ... but in general if you use uppercase or camelcase
> you're quite safe (there are some math symbols with uppercase but if you
> define your own commands you will probably not use those) ... mechanisms
> like tables that use \NC and so define them local
I see. Local commands are a good idea. I usually use camelcase, but
since I wanted to define some two-letter sequences, I thought I'd
better be cautious.
Nicola
___________________________________________________________________________________
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
___________________________________________________________________________________
prev parent reply other threads:[~2016-03-07 20:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-07 18:40 Nicola
2016-03-07 18:47 ` luigi scarso
2016-03-07 19:02 ` Nicola
2016-03-07 20:16 ` Hans Hagen
2016-03-07 20:30 ` Nicola [this message]
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='nbkodr$4po$1@ger.gmane.org' \
--to=nvitacolonna@gmail.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).