From: Andreas Schneider <aksdb@gmx.de>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Custom parameters/options for t-vim
Date: Tue, 30 Aug 2011 16:27:49 +0200 [thread overview]
Message-ID: <4E5CF365.2040908@gmx.de> (raw)
Hi,
I worked with t-vim a bit more and encountered a small problem with the
way vim handles syntax definitions. Some of them have several modes that
get activated by setting a variable first. For example the syntax "sh"
(shell scripts) can be enhanced for bash, ksh, etc.
Example:
let g:is_bash=1
set syntax=sh
Now a line like "export foo=bar" is highlighted differently than when I
would omit the "let g:is_bash=1".
Therefore I would propose another options to \setupvimtyping to specify
custom options to be passed to vim. Preferably they should be passed at
least before the "set syntax=..." line to make sure that this particular
case -- i.e. switching syntax modes -- works well (which may be the only
necessary case).
--
Best Regards,
Andreas
___________________________________________________________________________________
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 reply other threads:[~2011-08-30 14:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-30 14:27 Andreas Schneider [this message]
2011-08-29 21:35 ` Aditya Mahajan
2011-08-31 7:15 ` Andreas Schneider
2011-08-31 23:00 ` Aditya Mahajan
2011-09-03 6:58 ` Aditya Mahajan
2011-09-06 9:07 ` Andreas Schneider
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=4E5CF365.2040908@gmx.de \
--to=aksdb@gmx.de \
--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).