From: SebastianSturm@t-online.de (Sebastian Sturm)
Subject: Known nath bugs?
Date: Fri, 28 May 2004 17:42:00 +0200 [thread overview]
Message-ID: <8F2B73AE-B0BD-11D8-A6BA-0003939959D2@t-online.de> (raw)
Hello all,
is there a list of know nath bugs somewhere on the web? I tried to find
one using Google, but unfortunately without success.
The reason I'm asking this is that I'm encountering some problems with
the module and would like to know if they are common or if it's related
to my configuration. First of all, using the units module together with
nath doesn't seem to work - for instance, $1\Micro\Coulomb$ works as
expected without nath, but produces the error message "Please don't say
\def cs{...}, say \def\cs{...}" when used together with nath. I also
thought that delimiters like ( or [ should automatically adjust to the
formula they contain, but (\sum_{something}
\frac{something}{something}) only produces standard parentheses.
Commands like \lbrace or \lbrack work as expected, though.
If these problems are unknown, I can post a small example file and my
logfile.
Best regards,
Sebastian
next reply other threads:[~2004-05-28 15:42 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-28 15:42 Sebastian Sturm [this message]
2004-05-29 12:28 ` Sebastian Sturm
2004-05-29 14:13 ` Re[2]: " Giuseppe Bilotta
2004-05-29 21:20 ` Sebastian Sturm
2004-05-30 9:47 ` Re[4]: " Giuseppe Bilotta
2004-05-30 18:15 ` Sebastian Sturm
2004-06-01 13:50 ` Gary Pajer
2004-06-05 20:08 ` Re[6]: " Giuseppe Bilotta
2004-06-08 14:58 ` Gary Pajer
2004-06-08 22:20 ` Re[8]: " Giuseppe Bilotta
2004-06-05 20:09 ` Re[6]: " Giuseppe Bilotta
2004-06-06 9:44 ` Sebastian Sturm
2004-06-27 10:19 ` Re[8]: " Giuseppe Bilotta
2004-07-04 12:01 ` Sebastian Sturm
2004-07-05 9:46 ` Re[10]: " Giuseppe Bilotta
2004-06-01 18:13 ` Re[4]: " 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=8F2B73AE-B0BD-11D8-A6BA-0003939959D2@t-online.de \
--to=sebastiansturm@t-online.de \
--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).