From: Pablo Rodriguez <oinos@gmx.es>
To: ntg-context@ntg.nl
Subject: Re: type and typing comments for TeX and Lua
Date: Thu, 21 Dec 2017 20:53:11 +0100 [thread overview]
Message-ID: <960fe9d0-262b-b728-d743-ed7a99fae1fe@gmx.es> (raw)
In-Reply-To: <d887eb05-b2e6-f7f1-2078-ab33f2324447@wxs.nl>
On 12/20/2017 10:18 PM, Hans Hagen wrote:
> On 12/20/2017 8:45 PM, Pablo Rodriguez wrote:
>> [...]
>> Would it be possible that there are two SnippetComments for all lexers:
>> SnippetCommentMark and SnippetCommentText?
> > very low priority ... there is some logic behind these that i don't want
> to break
Then I will have to wait for that implementation. Sorry for not being
able to provide the patch myself.
scite is great for coloring, but it lacks the options from \setuptype
and \setuptyping. I don’t need escapes, but many of the other options.
I need both complete comment coloring (otherwise it is really hard for
newbies to see what a comment may be) and \setuptyping (and \setuptype)
options.
BTW, I’m afraid there is a bug with multiline comments in Lua. The first
line break is removed in multiline:
%~ \usemodule[scite] % to check the bug
\starttext
\startTEXpage[offset=2em]
\startLUA
--[[
multiline comment
]]--
---[[
multiline comment
]]---
\stopLUA
\stopTEXpage
\stoptext
Many thanks for your help again,
Pablo
--
http://www.ousia.tk
___________________________________________________________________________________
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
___________________________________________________________________________________
next prev parent reply other threads:[~2017-12-21 19:53 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-18 22:50 Pablo Rodriguez
2017-12-19 19:26 ` Aditya Mahajan
2017-12-19 21:29 ` Pablo Rodriguez
2017-12-19 23:20 ` Aditya Mahajan
2017-12-21 18:54 ` Pablo Rodriguez
2017-12-21 19:05 ` Aditya Mahajan
2017-12-21 20:49 ` Pablo Rodriguez
2017-12-21 21:53 ` Aditya Mahajan
2017-12-26 18:36 ` Pablo Rodriguez
2017-12-27 22:32 ` Aditya Mahajan
2017-12-20 11:53 ` Hans Hagen
2017-12-20 19:45 ` Pablo Rodriguez
2017-12-20 21:18 ` Hans Hagen
2017-12-21 19:53 ` Pablo Rodriguez [this message]
2017-12-21 16:04 Christoph Reller
2017-12-21 20:16 ` Pablo Rodriguez
2017-12-27 1:14 ` SteamedFish
2017-12-27 18:44 ` Pablo Rodriguez
2017-12-21 21:16 Christoph Reller
2017-12-26 18:07 ` Pablo Rodriguez
2017-12-27 18:53 ` Pablo Rodriguez
2017-12-28 7:38 Christoph Reller
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=960fe9d0-262b-b728-d743-ed7a99fae1fe@gmx.es \
--to=oinos@gmx.es \
--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).