From: Hans Hagen <j.hagen@xs4all.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>,
Christoph Reller <christoph.reller@gmail.com>
Subject: Re: Strange bug with obayspaces and tagging
Date: Thu, 26 Nov 2020 11:11:29 +0100 [thread overview]
Message-ID: <4f665e45-66c5-6317-a5b1-aaf587b06c61@xs4all.nl> (raw)
In-Reply-To: <CAO8LnPHR=7WHEGb6+bHV5ZQQp0he7PD=x46YoBA9UpfFgx6Raw@mail.gmail.com>
On 11/26/2020 10:47 AM, Christoph Reller wrote:
> Hi,
>
> With the currently latest version of ConTeXt LMTX 2020.11.25 21:42, this
> MNWE fails with the following error message:
>
> ----
>
> \setuptagging[state=start]
> \starttext
> \obeyspaces\obeylines
> patch
> \stoptext
>
> ----
>
> tex error > tex error on line 4 in file ./scratch1.tex: Valid
> keyword expected, likely 'plus'
>
> <line 3.4> pa
> tch
>
> 1 \setuptagging[state=start]
> 2 \starttext
> 3 \obeyspaces\obeylines
> 4 >> patch
> 5 \stoptext
>
> ----
>
> This may be a bug in the tagging feature.
i'll fix it
-----------------------------------------------------------------
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:[~2020-11-26 10:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-26 9:47 Christoph Reller
2020-11-26 10:11 ` 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=4f665e45-66c5-6317-a5b1-aaf587b06c61@xs4all.nl \
--to=j.hagen@xs4all.nl \
--cc=christoph.reller@gmail.com \
--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).