From: Nikolai Weibull <context-list@pcppopper.org>
Subject: nath catcode issues
Date: Sun, 4 Jul 2004 15:36:38 +0200 [thread overview]
Message-ID: <20040704133638.GA23652@puritan.pcp.ath.cx> (raw)
It seems that the code to enable catcode handling in nath math mode
isn't working. Currently, nath uses
\appendtoks
% \livechars@
\def({\delim@l 1\ch@lparenthesis}
\def){\delim@r 1\ch@rparenthesis}
\def[{\delim@l 1\o@lbrack}
\def]{\delim@r 1\o@rbrack}
\def>{\gt}
\def<{\lt}
\def!{\factorial}
\def,{\@comma}
\def;{\@semicolon}
\def`{\abbreviation}
% \killchars@
\to\everymath
to set it up, but as far as I can see this doesn't actually do anything
as \@comma doesn't get invoked for commas and \dots always renders like
\cdots. Am I missing something perhaps?
Furthermore,
\def\over{\n@err{Disabled command \string\over }
{No more a valid command. Replace {A \over B} with \frac A B.}}
\def\atop{\n@err{Disabled command \string\atop }
{No more a valid command. Use array instead.}}
\def\choose{\n@err{Disabled command \string\choose }
{No more a valid command. Replace {A \choose B} with \binom A B.}}
also messes up stuff in core-ref.tex for example:
! Disabled command \over.
\n@err ...rrhelp \expandafter {#2}\errmessage {#1}
\natherrormark
l.46 \indent\inchapter[definitions], \about
[definitions], covers the definit...
?
Which I don't quite understand, but core-ref.tex has the line
\definecommand over {\dospecialover}
which I suppose could be troublesome.
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 reply other threads:[~2004-07-04 13:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-04 13:36 Nikolai Weibull [this message]
2004-07-05 10:01 ` Giuseppe Bilotta
2004-07-05 10:44 ` Nikolai Weibull
2004-07-05 11:03 ` Giuseppe Bilotta
2004-07-05 12:42 ` Nikolai Weibull
2004-08-07 14:58 ` Giuseppe Bilotta
2004-08-08 19:28 ` Nikolai Weibull
2004-08-25 18:29 ` Giuseppe Bilotta
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=20040704133638.GA23652@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).