ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Fabrice Couvreur via ntg-context <ntg-context@ntg.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Cc: Fabrice Couvreur <fabrice1.couvreur@gmail.com>
Subject: Strange behavior of a macro
Date: Mon, 16 Aug 2021 16:28:08 +0200	[thread overview]
Message-ID: <CACyK-eopx54tMrKAh8g_OUBSb1DwM6n5L9yOwRrt+eSsY8rrOg@mail.gmail.com> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 1815 bytes --]

Hello,
I don't understand why this macro works with this simple example but return
the following error if I use it for chapters in my book.
Thanks
Fabrice

%%%%
\setupbodyfont
   [newcomputermodern-book,11pt]

\unexpanded\def\N{\math{\mathbb{N}}\autoinsertnextspace}

\defineenumeration
   [test]
   [title=yes,
    text={Test},
    style=italic]

\starttext
\N
\starttest
\m{\forall n \in \N}
\stoptest
\stoptext

%%%%
tex error       > tex error on line 64 in file ./terminale_suites_2.tex:
Use of \N doesn't match its definition



<line 3.64>
              Soient \u, \v deux suites définies sur \N,
     \m{l} et \m{l'} deux réels.

54                 \startitem
55                   \u converge vers \m{l},
56                 \stopitem
57               \stopitemize
58               alors \m{l\geqslant 0}.
59             \stopproposition
60             \startremarque
61               Nous retiendrons que le passage à la limite sur une
inégalité stricte restitue une inégalité large.
62             \stopremarque
63             \startcorollaire
64 >>            Soient \u, \v deux suites définies sur \N, \m{l} et \m{l'}
deux réels.
65
66               Si
67
68               \startitemize
69                 \startitem
70                   les suites \u et \v convergent respectivement vers
\m{l} et \m{l'},
71                 \stopitem
72                 \startitem
73                   \m{\forall n \in\mathbb{N}, \thinspace u_n>v_n},
74                 \stopitem
If you say, e.g., '\def\a1{...}', then you must always put '1' after '\a',
since control sequence names are made up of letters only. The macro here
has not
been followed by the required stuff, so I'm ignoring it.
mtx-context     | fatal error: return code: 256
%%%%

[-- Attachment #1.2: Type: text/html, Size: 3511 bytes --]

[-- Attachment #2: Type: text/plain, Size: 493 bytes --]

___________________________________________________________________________________
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:[~2021-08-16 14:28 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-16 14:28 Fabrice Couvreur via ntg-context [this message]
2021-08-16 14:45 ` Hans Hagen via ntg-context

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=CACyK-eopx54tMrKAh8g_OUBSb1DwM6n5L9yOwRrt+eSsY8rrOg@mail.gmail.com \
    --to=ntg-context@ntg.nl \
    --cc=fabrice1.couvreur@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).