ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <pragma@wxs.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: I can't change startitemize[n]--> startitemize[1]
Date: Thu, 23 Jul 2009 18:04:30 +0200	[thread overview]
Message-ID: <4A688A0E.1070906@wxs.nl> (raw)
In-Reply-To: <alpine.LNX.2.00.0907231144340.11304@ybpnyubfg.ybpnyqbznva>

Aditya Mahajan wrote:

> \def\defineSOMETHING%
>   {\dodoubleargument\dodefineSOMETHING}
> 
> \def\dodefineSOMETHING[#1][#2]%
>  {\setvalue{#1}{\dododefineSOMETHING[#2]}

some do, but sometimes redefinition is quite legal; it happens that 
'note' and 'symbol' are pretty core

the convention (as mentioned) is more or less to use UpperCase names for 
your own commands and UPPERCASE for logo's and abbreviations (but these 
can have an optional namespace)

kind of tricky are colors and fonts as they have no namespace so i often 
end up with ThisColor or ThatFont

> I meant with commands like \defineSOMETHING above. For example, I once 
> did \definecolor[page][s=0.9] instead of what I normally do: 
> \definecolor[pagecolor][s=0.9]. Took a while to figure out what was 
> going wrong. Some of Xan's error were due to similar things, 
> \defineSOMETHING[note], \defineSOMETHING[symbol], etc. If all these 
> commands issued a warning that you are redefining existing macro, 
> debugging will be much easier. And if you know what you are doing, we 
> could have
> 
> \redefinecolor[page][s=0.9]
> 
> that does not issue a warning. Or the easier to implemnet:
> 
> \setupcolors[check=error|warn|ignore]

maybe later, as it clutters the code; maybe after the mkii->mkiv cleanup

Hans

-----------------------------------------------------------------
                                           Hans Hagen | PRAGMA ADE
               Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
      tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com
                                              | 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://tex.aanhet.net
archive  : https://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________


  parent reply	other threads:[~2009-07-23 16:04 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-23 12:06 Xan
2009-07-23 12:45 ` Wolfgang Schuster
2009-07-23 14:05   ` Hans Hagen
2009-07-23 14:33     ` Xan
2009-07-23 14:37       ` Hans Hagen
2009-07-23 14:48         ` luigi scarso
2009-07-23 14:58           ` Wolfgang Schuster
2009-07-23 15:05             ` luigi scarso
2009-07-23 15:10               ` Wolfgang Schuster
2009-07-23 15:16                 ` luigi scarso
2009-07-23 15:26                   ` luigi scarso
2009-07-23 15:33                   ` Wolfgang Schuster
2009-07-23 15:46                     ` luigi scarso
2009-07-23 15:05           ` Aditya Mahajan
2009-07-23 15:11             ` luigi scarso
2009-07-23 15:16             ` Wolfgang Schuster
2009-07-23 15:52               ` Aditya Mahajan
2009-07-23 15:57                 ` luigi scarso
2009-07-23 16:04                 ` Hans Hagen [this message]
2009-07-23 15:42         ` Xan

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=4A688A0E.1070906@wxs.nl \
    --to=pragma@wxs.nl \
    --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).