Parse oddity with modes, compilation halts
![](https://secure.gravatar.com/avatar/e07e15a8be3c4c1723f5a0397bc17424.jpg?s=120&d=mm&r=g)
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
![](https://secure.gravatar.com/avatar/49e63acb01f2ca80efce7eed08310ce8.jpg?s=120&d=mm&r=g)
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 -----------------------------------------------------------------
participants (2)
-
Hans Hagen
-
Rik Kabel