From: Nikolai Weibull <context-list@pcppopper.org>
Subject: Re: \doifnextcharelse problem
Date: Thu, 26 Feb 2004 20:05:25 +0100 [thread overview]
Message-ID: <20040226190525.GH26896@puritan.pcp.ath.cx> (raw)
In-Reply-To: <6.0.1.1.2.20040226185816.01febec0@server-1>
* Hans Hagen <pragma@wxs.nl> [Feb 26, 2004 19:10]:
> go the etex way:
great! thanks, that worked.
> no % are needed after a \cs:
hm, OK. This is a good reason why it would be good to have a tex
programming reference, so that one'd know when it's necessary and when
it's not.
> I assume that you know that \setcatcodes is an internal command
yeah, I saw it somewhere. I figured that it was a good name though and
that I'd use it too. I figured that the \unprotect deal with the
nameclash. Am I, in fact, overruling the internal one now? If so, how
should one avoid cases like this? Should I have all my module's
commands CamelCased?
Also, is there some repository of CONTEXT modules out there? I can't
find a reference on pragma-ade.com nor ntg.nl, but maybe I've missed it.
Anyway, thanks Hans for such a quick and thorough response, and also for
a great typesetting environment; TeX has never been easier,
nikolai
--
::: name: Nikolai Weibull :: aliases: pcp / lone-star / aka :::
::: born: Chicago, IL USA :: loc atm: Gothenburg, Sweden :::
::: page: www.pcppopper.org :: fun atm: gf,lps,ruby,lisp,war3 :::
main(){printf(&linux["\021%six\012\0"],(linux)["have"]+"fun"-97);}
next prev parent reply other threads:[~2004-02-26 19:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-26 16:38 Nikolai Weibull
2004-02-26 18:00 ` Hans Hagen
2004-02-26 19:05 ` Nikolai Weibull [this message]
2004-02-27 7:53 ` Hans Hagen
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=20040226190525.GH26896@puritan.pcp.ath.cx \
--to=context-list@pcppopper.org \
--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).