From: Hans Hagen <pragma@wxs.nl>
Subject: Re: \doifnextcharelse problem
Date: Fri, 27 Feb 2004 08:53:50 +0100 [thread overview]
Message-ID: <6.0.1.1.2.20040227085208.0202fec0@server-1> (raw)
In-Reply-To: <20040226190525.GH26896@puritan.pcp.ath.cx>
At 20:05 26/02/2004, you wrote:
>commands CamelCased?
For third party extensions:
- low level: \BNFsomething
- high level: whatever you want (often the start/setup will not clash
that much, maybe we need to setup a registration system)
for macros in documents:
- \CamelCased
is fine
Hans
prev parent reply other threads:[~2004-02-27 7:53 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
2004-02-27 7:53 ` Hans Hagen [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=6.0.1.1.2.20040227085208.0202fec0@server-1 \
--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).