ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Enzo Cordes <plink@veribox.net>
Cc: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: character redefinition environment
Date: Mon, 06 Nov 2006 17:40:40 +0100	[thread overview]
Message-ID: <454F6588.4030502@veribox.net> (raw)
In-Reply-To: <454E1C00.6040906@wxs.nl>

Many thanks, Hans!

I wasn't sure I made myself clear, but defineactivecharacter does the 
job very very nicely. One day I understand one of its many definitions - 
especially the \uccode tilde business, which is probably necessary for 
the TeX mastication process ;-)

Enzo


Hans Hagen wrote:
> | is already active, but not b
> 
> \bgroup
> \catcode`B=\active
> \def\start...
> 
> \egroup
> 
> otherwise a 'character B' and not an 'active character B' ends up in the 
> definition
> 
> This may be easier:
> 
> \def\Whatever
>  {\defineactivecharacter B {[oeps]}}
> 
> bla bla \start \Whatever B \stop ble bla

      reply	other threads:[~2006-11-06 16:40 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-05 14:49 Enzo Cordes
2006-11-05 17:14 ` Hans Hagen
2006-11-06 16:40   ` Enzo Cordes [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=454F6588.4030502@veribox.net \
    --to=plink@veribox.net \
    --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).