From: SebastianSturm@t-online.de (Sebastian Sturm)
Subject: Re: Re[4]: Known nath bugs?
Date: Sun, 30 May 2004 20:15:11 +0200 [thread overview]
Message-ID: <4A3EF82B-B265-11D8-B89A-0003939959D2@t-online.de> (raw)
In-Reply-To: <15810421728.20040530114757@iol.it>
Hi,
> Nath is a very complex module, easily broken. If you can
> privately send me your preamble we might be able to find what
> was breaking it. Or you can try it yourself: move it up line by
> line until delimiters don't work anymore: you'll find what
> makes it bomb :)
OK, I'll try that. At the moment I'm having all kinds of issues with
nath (even without any preamble at all), like \binom{\frac 12}{a} not
working, \to, \ot and \otto arrows not adjusting to the lengths of
their subscripts, etc... and I can hardly imagine that all of these are
nath bugs, so maybe something's wrong with my TeX installation. I'm
using the latest i-Installer teTeX for MacOS X package (with non-beta
ConTeXt version), configuration files unchanged.
So if someone else is using nath with Gerben Wieda's teTeX
installation, it would be helpful to know if he/she is experiencing
similar problems.
Anyway, the nath module looks very promising; I'm really looking
forward to its next revision!
Best regards,
Sebastian
next prev parent reply other threads:[~2004-05-30 18:15 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-28 15:42 Sebastian Sturm
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 [this message]
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=4A3EF82B-B265-11D8-B89A-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).