From: Nicola <nvitacolonna@gmail.com>
To: ntg-context@ntg.nl
Subject: Re: Custom syntax highlighting
Date: Wed, 2 Mar 2016 09:46:40 +0100 [thread overview]
Message-ID: <nb699g$lml$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:
>
> I do not load the default vimrc, because that drastically slows down the
> module.
That makes sense. So, Vim is run with something like `vim -u NONE`, I guess.
> Instead, there is an option to create a specific vimrc using:
>
> \startvimrc[name=pgsql]
> let g:sql_type_default='pgsql'
> \stopvimrc
>
> and then
>
> \definevimtyping[SQL][..., vimrc=pgsql, ...]
>
> By default, the script searches everything in `runtimepath`. If your local
> vim folder is not in runtimepath, you can set the runtimepath in the vimrc
> above.
I had to set both runtimepath and nocompatible. Maybe this should be noted
in the docs, or the module could run `vim -u NONE -N` (who needs compatible
nowadays?). So, for future reference, this works:
\startvimrc[name=pgsql]
set nocompatible
set runtimepath+=~/.vim/bundle/pgsql
let g:sql_type_default='pgsql'
% ...
\stopvimrc
>
>> 2) Are pscolor and blackandwhite the only possibilities to customize the
>> colors? This is important, I need the syntax highlighting to match my
>> document's colors.
>
> It is relatively easy to tune the color scheme. See, for example how
> pscolor is defined:
> https://github.com/adityam/filter/blob/cc9d9017bfdd7fe0d67b4723570e960ec6c52e43/t-vim.tex#L280
>
>
> You can create similar mappings for your favorite color scheme (It does
> require a bit of knowledge of vim syntax groups).
Perfect, thanks!
>> Finally, your Readme tells to use \definevimtyping[...][...], but I have
>> found
>> that I need to use put all the options together: \defienvimtyping[...].
>
> What I mean is \definevimtyping[SQL][numbering=on], etc.
Ops, dumb oversight on my part.
Thanks for your help and your amazing module,
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 8:46 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 [this message]
2016-03-02 14:45 ` Aditya Mahajan
2016-03-02 15:23 ` Nicola
2016-03-02 11:06 ` Nicola
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='nb699g$lml$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).