From: Nicola <nvitacolonna@gmail.com>
To: ntg-context@ntg.nl
Subject: Re: Custom syntax highlighting
Date: Wed, 2 Mar 2016 12:06:34 +0100 [thread overview]
Message-ID: <nb6hfr$tgn$1@ger.gmane.org> (raw)
In-Reply-To: <alpine.OSX.2.02.1603012105320.8080@nqv-znpobbx>
On 2016-03-02 02:14:33 +0000, Aditya Mahajan said:
> On Tue, 1 Mar 2016, Nicola wrote:
>
>> On 2016-03-01 15:35:07 +0000, Aditya Mahajan said:
>>
>>> On Tue, 1 Mar 2016, Nicola wrote:
>>>
>>>> I'm using the latest beta, and I need syntax coloring for SQL
>>>> (PostgreSQL variant). According to the wiki, there is no SQL
>>>> syntax coloring available for MKIV yet, but I'd be happy to
>>>> be wrong :)
>>>
>>> You can use the vim module:
>>>
>>> https://github.com/adityam/filter/blob/master/vim-README.md
I have a relatively minor problem with linked highlight groups.
As far as I can see, the module resolves linked groups so that,
for example, if String links to Constant, then the generated code
for 'a string' will be something like \SYN[Constant]{'a string'},
rather than \SYN[String]{'a string'}. In my specific case, strings
use the sqlString group, which links by default to String, which in
turn links to Constant.
Is there a way to decouple linked highlight groups, so that, for
example, I may distinguish Constant from String? I have already
tried to put commands like
hi! clear sqlString
hi! link String NONE
etc...
in the vimrc block, to no avail.
Nicola
___________________________________________________________________________________
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://tex.aanhet.net
archive : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2016-03-02 11:06 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-01 15:26 Nicola
2016-03-01 15:35 ` Aditya Mahajan
2016-03-01 18:14 ` Nicola
2016-03-02 2:14 ` Aditya Mahajan
2016-03-02 8:46 ` Nicola
2016-03-02 14:45 ` Aditya Mahajan
2016-03-02 15:23 ` Nicola
2016-03-02 11:06 ` Nicola [this message]
2016-03-02 11:20 ` Nicola
2016-03-02 18:21 ` Nicola
2016-03-02 19:34 ` Aditya Mahajan
2016-03-02 19:58 ` Nicola
2016-03-02 20:11 ` Aditya Mahajan
2016-03-02 20:29 ` Nicola
2016-03-01 21:53 ` Hans Hagen
2016-03-02 8:56 ` Nicola
2016-03-02 9:13 ` Hans Hagen
2016-03-02 10:45 ` Nicola
2016-03-02 23:16 ` Alan BRASLAU
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='nb6hfr$tgn$1@ger.gmane.org' \
--to=nvitacolonna@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).