* Parse oddity with modes, compilation halts
@ 2018-01-02 18:48 Rik Kabel
2018-01-02 21:02 ` Hans Hagen
0 siblings, 1 reply; 2+ messages in thread
From: Rik Kabel @ 2018-01-02 18:48 UTC (permalink / raw)
To: mailing list for ConTeXt users
[-- Attachment #1.1: Type: text/plain, Size: 463 bytes --]
Consider the following example:
When this is run with --mode=vim, all is well. When the mode is not set,
compilation fails. I suspect that the parser is scanning for the closing
curlie of \inlineTEX but never sees it.
\starttext
\startmode[vim]
\usemodule[t-vim]
\definevimtyping[TEX][syntax=context]
\inlineTEX{%}
\stopmode
‽
\stoptext
Is there any work-around to prevent this, other than avoiding it completely?
--
Rik
[-- Attachment #1.2: Type: text/html, Size: 907 bytes --]
[-- Attachment #2: Type: text/plain, Size: 492 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
___________________________________________________________________________________
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: Parse oddity with modes, compilation halts
2018-01-02 18:48 Parse oddity with modes, compilation halts Rik Kabel
@ 2018-01-02 21:02 ` Hans Hagen
0 siblings, 0 replies; 2+ messages in thread
From: Hans Hagen @ 2018-01-02 21:02 UTC (permalink / raw)
To: mailing list for ConTeXt users, Rik Kabel
On 1/2/2018 7:48 PM, Rik Kabel wrote:
> Consider the following example:
>
> When this is run with --mode=vim, all is well. When the mode is not set,
> compilation fails. I suspect that the parser is scanning for the closing
> curlie of \inlineTEX but never sees it.
>
> \starttext
> \startmode[vim]
> \usemodule[t-vim]
> \definevimtyping[TEX][syntax=context]
> \inlineTEX{%}
> \stopmode
> ‽
> \stoptext
>
> Is there any work-around to prevent this, other than avoiding it completely?
% \enablemode[test]
\starttext
\startbuffer[test]
\type{%}
\stopbuffer
\startmode[test]
\getbuffer[test]
\stopmode
\startnotmode[test]
!
\stopnotmode
\stoptext
-----------------------------------------------------------------
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
___________________________________________________________________________________
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2018-01-02 21:02 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2018-01-02 18:48 Parse oddity with modes, compilation halts Rik Kabel
2018-01-02 21:02 ` Hans Hagen
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).