ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <j.hagen@xs4all.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>,
	Otared Kavian <otared@gmail.com>
Subject: Re: Bug in latest LMTX
Date: Wed, 22 Jul 2020 08:33:21 +0200	[thread overview]
Message-ID: <619c2666-ef1d-7d9b-4cf7-8586660c561e@xs4all.nl> (raw)
In-Reply-To: <43188827-1BB6-4E4A-B72A-52F3B1D9E4DB@gmail.com>

On 7/22/2020 5:43 AM, Otared Kavian wrote:
> Hi Hans,
> 
> It seems that \cap is not anymore defined in the latest LMTX: the following gives an error
> 
> \starttext
> $A \cap B$
> \stoptext
> 
> with current version: 2020.07.21 18:39.
> 
> Also, I would like to place a request about the reporting of errors: can we get back the nice reporting of errors we had a few months ago?
> Indeed while a few months ago the reporting of errors was extremeley clear and helpful, now one gets a cryptic message like this in the html file produced:
> 
> Error	   ! Missing } inserted
> File 	   chapitre-1.tex
> Line 	   834
> 
> Of course there is no missing } error in that file and that line, and one has to spend a lot of time to find what the error would be. In this case I could guess that the error comes from the fact that \cap is not defined, but it wasn't easy (the file used to typeset correctly with version 2020.07.13, and it typesets correctly with mkiv).
> In eralier versions, ConTeXt would tell the user
> 	undefined control sequence \cap
> and one could fix things very quickly.

\cap is defined (just put \meaning in front), it just doesn't have the 
meaning you want in math (a symbol), so it scane for an argument

fixed in next (the running out of text is on the agenda for later, part 
of something larger)

Hans


-----------------------------------------------------------------
                                           Hans Hagen | PRAGMA ADE
               Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
        tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl
-----------------------------------------------------------------
___________________________________________________________________________________
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
___________________________________________________________________________________

      reply	other threads:[~2020-07-22  6:33 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-22  3:43 Otared Kavian
2020-07-22  6:33 ` Hans Hagen [this message]

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=619c2666-ef1d-7d9b-4cf7-8586660c561e@xs4all.nl \
    --to=j.hagen@xs4all.nl \
    --cc=ntg-context@ntg.nl \
    --cc=otared@gmail.com \
    /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).