ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Wolfgang Schuster <schuster.wolfgang@googlemail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: One-off theorem titles
Date: Sun, 6 Mar 2011 09:44:33 +0100	[thread overview]
Message-ID: <FD4B34C2-D9D0-4FDD-95F1-7F196CD98BDB@gmail.com> (raw)
In-Reply-To: <alpine.LNX.2.01.1103051757300.1228@ybpnyubfg.ybpnyqbznva>


Am 06.03.2011 um 00:03 schrieb Aditya Mahajan:

> On Fri, 4 Mar 2011, Hans Hagen wrote:
> 
>> On 4-3-2011 7:05, Wolfgang Schuster wrote:
>> 
>>> In which are these alternatives are better than my module__command, you replace only the _ by !
>> 
>> because an ! stands out; anyway, we should avoid multiple _ in a row
>> 
>> (i'll put a few mkvi modules in the core to get a feeling .. using _ does not always look better btw)
> 
> Here is an experiment with @ and _. I would prefer to change @ to :: (but for that we would need to change the ptrcatcodes).


+1 for “:”

I can then change this

\unexpanded\def\annotation_placement_define
  {\dodoubleargument\annotation_placement__define}

\def\annotation_placement__define[#name][#command]%
  {\setvalue{annotation:#name}{#command}}

to (took the “o” from latex3 :)

\unexpanded\def\annotation_placement_define
  {\dodoubleargument\annotation_placement_define:oo}

\def\annotation_placement_define:oo[#name][#command]%
  {\setvalue{annotation:#name}{#command}}

Wolfgang

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


  parent reply	other threads:[~2011-03-06  8:44 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
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                   ` Wolfgang Schuster [this message]
2011-03-06  8:17                 ` One-off theorem titles 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=FD4B34C2-D9D0-4FDD-95F1-7F196CD98BDB@gmail.com \
    --to=schuster.wolfgang@googlemail.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).