From: Nicola <nvitacolonna@gmail.com>
To: ntg-context@ntg.nl
Subject: Custom color schemes in t-vim
Date: Thu, 14 May 2020 10:42:47 -0000 (UTC) [thread overview]
Message-ID: <r9j7b7$1k16$1@ciao.gmane.io> (raw)
Quick question: Is \startcolorscheme... \stopcolorscheme (still)
supported by t-vim?
In a template I wrote long time ago to typeset code, I have:
\usemodule[vim]
\unprotect
\startcolorscheme[oceansunset]
\definesyntaxgroup[Comment][\c!color={colortwo},\c!style=italic]
% etc.
\stopcolorscheme
\protect
which I use as described in the wiki:
\definevimtyping
[...]
[...
alternative=oceansunset,
...]
But that does not seem to have any effect (if I change the colors, the
syntax highlighting does not change). I can use pscolor and
blackandwhite, though. I see that \startcolorscheme is not documented,
so maybe there is another mechanism?
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 reply other threads:[~2020-05-14 10:42 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-14 10:42 Nicola [this message]
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
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='r9j7b7$1k16$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).