From: "j. van den hoff" <veedeehjay@gmail.com>
To: "mailing list for ConTeXt users" <ntg-context@ntg.nl>,
"Hans Hagen" <pragma@wxs.nl>
Subject: Re: problem with math: "\left" leads to "udefined symbol" --solved (sort of)
Date: Tue, 24 Jan 2017 16:47:22 +0100 [thread overview]
Message-ID: <op.yukt48u4p7eajd@marco.fz-rossendorf.de> (raw)
In-Reply-To: <ab7b28d3-e1f8-1569-67ff-d3f6e47cbefd@wxs.nl>
well after incrementally deleting most everything from my document I now
seem to have a reproducible example:
8<--------------------------------------------
\definesynonyms[MySymbol][MySymbols][\meaning]
\MySymbol [whaever] {this} { means }
\starttext
\startformula
x = \left ( 1 + 2 \right )
\stopformula
\stoptext
8<--------------------------------------------
the apparent "culprit" is the presence of the `\definesynonyms' stuff.
without it the rest (identical to your minimal example) compiles. with it
it does not... remember that I am really unexperienced with `context': at
the time (2 years ago), when I first tried this, it worked. I now realize
(after reading up on the `definesynonyms' syntax again ...) that
in the definition a _command_ has to go into the third bracket. seemingly
at the time I was just putting a placeholder `\meaning' there (never
attempting to use it as a command acting on the explanatory text for that
symbol definition but only wanting a glossary.
the strange thing (for me) is that this worked just fine two years ago,
now it does produce a very strange error as described. question is why.
but replacing `\meaning' by `\infull' suffices to restore sane behaviour.
while I understand, that I did something stupid (putting a non-existent
command `\meaning' in the definition), I would have presumed that this
might trigger an error at that place rather than making `\left (' suddenly
an undefined control sequence. any explanation what is going on here would
be greatly appreciated.
On Tue, 24 Jan 2017 15:02:38 +0100, Hans Hagen <pragma@wxs.nl> wrote:
> this just works here ... so can others confirm it?
> \starttext
> \startformula
> x = \left ( 1 + 2 \right )
> \stopformula
> \stoptext
--
Using Opera's revolutionary email client: http://www.opera.com/mail/
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2017-01-24 15:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-24 10:33 problem with math: "\left" leads to "udefined symbol" j. van den hoff
2017-01-24 13:15 ` Hans Hagen
2017-01-24 13:33 ` j. van den hoff
2017-01-24 14:02 ` Hans Hagen
2017-01-24 14:15 ` luigi scarso
2017-01-24 14:54 ` j. van den hoff
2017-01-24 15:02 ` Roger Mason
2017-01-24 15:47 ` j. van den hoff [this message]
2017-01-24 16:34 ` problem with math: "\left" leads to "udefined symbol" --solved (sort of) 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=op.yukt48u4p7eajd@marco.fz-rossendorf.de \
--to=veedeehjay@gmail.com \
--cc=ntg-context@ntg.nl \
--cc=pragma@wxs.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).