From: Hans Hagen <j.hagen@xs4all.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>,
Hans van der Meer <havdmeer@ziggo.nl>
Subject: Re: hang error
Date: Thu, 8 Jul 2021 16:00:02 +0200 [thread overview]
Message-ID: <799a08ca-20f7-ab33-7ab4-d1c5038aee52@xs4all.nl> (raw)
In-Reply-To: <0F3E2349-1AE8-4C8D-B057-B83F6EBDAE1E@ziggo.nl>
On 7/8/2021 2:16 PM, Hans van der Meer wrote:
> Why this: normal plain TeX macro \hang giving an Undefined control
> sequence error in ConTeXt?
> This MWE shows it:
> \starttext
> \hang
> \stoptext
>
> I would not expect basic plain macro's to crash. If it is intended
> behaviour I do not think that is the road to go, because this
> invalidates older documents. But maybe it is just an error in the dis
> tribution.
wel, je vraagt er om .. \hang gobbled tot er een \par (equivalent) dat
eea afsluit ... er is een reden waarom we \start .. \stop hebben -)
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
___________________________________________________________________________________
prev parent reply other threads:[~2021-07-08 14:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-08 12:16 Hans van der Meer
2021-07-08 14:00 ` 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=799a08ca-20f7-ab33-7ab4-d1c5038aee52@xs4all.nl \
--to=j.hagen@xs4all.nl \
--cc=havdmeer@ziggo.nl \
--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).