From: Christoph Reller <christoph.reller@gmail.com>
To: ntg-context <ntg-context@ntg.nl>
Subject: Re: Verbatim typing and compound breakpoints
Date: Tue, 1 Sep 2020 11:10:22 +0200 [thread overview]
Message-ID: <CAO8LnPFvJXA0Qovwt5Z3t1ZrPqvRQ2QtWNfw-+Zinii9sbpN_Q@mail.gmail.com> (raw)
In-Reply-To: <CAO8LnPEFCWxnZ9=GAZTy0W_9PvsKK6YbBjTT=kznKzGsyLx6Kg@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 665 bytes --]
On Tue, Sep 1, 2020 at 10:50 AM Christoph Reller <christoph.reller@gmail.com>
wrote:
> I am using ConTeXt LMTX 2020.08.28 13:58 with the following M(N)WE:
>
> \definetype[typeLUA][option=LUA]
> \setbreakpoints[compound]
> \starttext
> \typeLUA{function(argument)}
> \stoptext
>
> Sadly, it does not compile.
>
I found that resetting the breakpoints within the typing command works:
\setbreakpoints[compound]
\definetype[typeLUA][option=LUA, command=\resetbreakpoints]
\starttext
\typeLUA{function(argument)}\par
If compound break points are enabled then this text line is broken after
the slash/next line.
\stoptext
Nonetheless: Is this bug?
Cheers, Christoph
[-- Attachment #1.2: Type: text/html, Size: 1131 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
___________________________________________________________________________________
prev parent reply other threads:[~2020-09-01 9:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-01 8:50 Christoph Reller
2020-09-01 9:10 ` Christoph Reller [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=CAO8LnPFvJXA0Qovwt5Z3t1ZrPqvRQ2QtWNfw-+Zinii9sbpN_Q@mail.gmail.com \
--to=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).