From: Nicola <nvitacolonna@gmail.com>
To: ntg-context@ntg.nl
Subject: Re: Custom color schemes in t-vim
Date: Sun, 17 May 2020 08:34:07 -0000 (UTC) [thread overview]
Message-ID: <r9qstv$1dgv$1@ciao.gmane.io> (raw)
In-Reply-To: <nycvar.YAK.7.77.849.2005170340490.225319@nqv-guvaxcnq>
On 2020-05-17, Aditya Mahajan <adityam@umich.edu> wrote:
>> Since I already map the minor groups to preferred groups in `t-vim`, I think
>> that a good compromise is to enable the minor groups by default. I can do
>> that by adding statements similar to those above in `2context.vim`. This will
>> not have any visual impact on any existing code, but will allow those who
>> want to tweak the highlighting of minor groups to define their own syntax
>> highlighting.
>
> Uploaded a new version with a fix.
Thanks for looking into it. I will download and test that soon.
A couple of remarks:
1. In one of my old documents, I had this command inside the colorscheme
block:
\setups{vim-minor-groups}
Was that to achieve the same purpose?
2. The wiki has no mention of \startcolorscheme... \stopcolorscheme or
\setups. An example of two would be very welcome!
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://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2020-05-17 8:34 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-14 10:42 Nicola
2020-05-14 15:44 ` Aditya Mahajan
2020-05-16 11:34 ` Nicola
2020-05-16 14:46 ` Aditya Mahajan
2020-05-16 15:03 ` Aditya Mahajan
2020-05-16 19:24 ` Nicola
2020-05-17 0:42 ` Aditya Mahajan
2020-05-17 6:36 ` Aditya Mahajan
2020-05-17 7:41 ` Aditya Mahajan
2020-05-17 8:34 ` Nicola [this message]
2020-05-17 10:27 ` Nicola
2020-05-17 15:21 ` Aditya Mahajan
2020-05-18 5:30 ` Aditya Mahajan
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='r9qstv$1dgv$1@ciao.gmane.io' \
--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).