From: Nigel King <nigel@nigelking.me.uk>
To: Context News Group <ntg-context@ntg.nl>
Subject: \infull not working
Date: Wed, 18 Nov 2020 12:35:08 +0000 [thread overview]
Message-ID: <6E232E9B-1753-4B8E-8789-5308261DF86B@nigelking.me.uk> (raw)
Dear Group,
Thanks for your excellent work.
I have just got a new computer and installed Context as I normally do. Unfortunately there appears to be a bug, unless I have done something wrong. \infull appears not to be working. I have used the following test file which is from the wiki but split the line with \infull{Ch} in two to be certain.
\definesynonyms[test][tests][\infull]
\setupsynonyms[test][criterium=all]
\test{ITU}{International Telecommunication Union}
\test{MID}{Maritime Identification Digit}
\test{Ch}{Switzerland}
\starttext
The \ITU\ is an
organisation in \infull{Ch}
\subject{Short is nice}
\placelistoftests
\stoptext
The log message has this in it.
tex error > tex error on line 12 in file /Users/nki001/OneDrive/MyDocuments/Context/NGAForIreland/test.tex: Undefined control sequence
<line 4.12> organisation in \infull
{Ch}
2
3 \setupsynonyms[test][criterium=all]
4
5 \test{ITU}{International Telecommunication Union}
6 \test{MID}{Maritime Identification Digit}
7 \test{Ch}{Switzerland}
8
9 \starttext
10
11 The \ITU\ is an
12 >> organisation in \infull{Ch}
13
Thoughts?
Nigel King
___________________________________________________________________________________
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 reply other threads:[~2020-11-18 12:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-18 12:35 Nigel King [this message]
2020-11-18 14:19 ` Hans Hagen
2020-11-18 15:12 ` Nigel King
2020-11-18 15:49 ` 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=6E232E9B-1753-4B8E-8789-5308261DF86B@nigelking.me.uk \
--to=nigel@nigelking.me.uk \
--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).