ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Aditya Mahajan <adityam@umich.edu>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: One-off theorem titles
Date: Sat, 5 Mar 2011 17:15:11 -0500 (EST)	[thread overview]
Message-ID: <alpine.LNX.2.01.1103051714010.1228@ybpnyubfg.ybpnyqbznva> (raw)
In-Reply-To: <AANLkTin3LvZyhzw_tVTUfBrFoFMEx64jpp0Z=QBiDH-6@mail.gmail.com>

On Fri, 4 Mar 2011, luigi scarso wrote:

> On Fri, Mar 4, 2011 at 11:33 AM, Hans Hagen <pragma@wxs.nl> wrote:
>> On 4-3-2011 12:55, Aditya Mahajan wrote:
>>
>>> I also like \<module>_<command>. That is better than \<module><command>
>>> that I have been using. Of course, this means that _ should not have its
>>> usual meaning. I haven't checked on how \unprotect works in MkII. If it
>>> makes _ a letter, then I'll switch to \<module>_<command>.
>>
>> the main disadvantage of _ (at least in the past) is that it can get
>> invisible on a low res screen
>>
>>> Another option might be to use \<module>.<command> with . having the
>>> right catcode. That will give macro names a more OOP feel.
>>
>> indeed, but unfortunately it clashes with . being other in dimensions
>> (althoug i can imagine that we patch luatex to accept it)
> why not
> \<module>:<command>

Wrong catcode :-(

I would prefer the C++ style

<module>::<command>

A single : is not visually distinct.

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


  reply	other threads:[~2011-03-05 22:15 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.1142.1298911160.4223.ntg-context@ntg.nl>
2011-03-03  8:05 ` S Barmeier
2011-03-03  8:43   ` Otared Kavian
2011-03-03 14:18   ` Wolfgang Schuster
2011-03-03 18:18     ` Aditya Mahajan
2011-03-03 18:31       ` Wolfgang Schuster
2011-03-03 23:55         ` Aditya Mahajan
2011-03-04 10:33           ` Hans Hagen
2011-03-04 10:36             ` luigi scarso
2011-03-05 22:15               ` Aditya Mahajan [this message]
2011-03-04 18:05             ` Wolfgang Schuster
2011-03-04 18:56               ` Hans Hagen
2011-03-05 23:03                 ` Aditya Mahajan
2011-03-06  5:39                   ` Underscore catcode in MkII (was Re: One-off theorem titles) Aditya Mahajan
2011-03-06 11:07                     ` Hans Hagen
2011-03-06 16:59                       ` Aditya Mahajan
2011-03-06  8:44                   ` One-off theorem titles Wolfgang Schuster
2011-03-06  8:17                 ` Wolfgang Schuster
2011-03-04 10:36           ` Hans Hagen
2011-03-03 18:07   ` Aditya Mahajan
     [not found] <mailman.1223.1299163042.4223.ntg-context@ntg.nl>
2011-03-03 15:00 ` S Barmeier
2011-03-03 15:24   ` 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=alpine.LNX.2.01.1103051714010.1228@ybpnyubfg.ybpnyqbznva \
    --to=adityam@umich.edu \
    --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).