From: Nikolai Weibull <mailing-lists.context-users@rawuncut.elitemail.org>
Subject: Re: TeX + Metapost syntax highlighting in Vim
Date: Sat, 24 Sep 2005 23:41:21 +0200 [thread overview]
Message-ID: <20050924214121.GA8992@puritan.pnetwork> (raw)
In-Reply-To: <e5d3f265050714121946f97d11@mail.gmail.com>
(OK, this is old, but I finally did something about it.)
VnPenguin wrote:
> Just tested your context.vim under vim 6.3.x; It's better than
> tex/latex standard syntax in vim 6.3 IMHO.
>
> I have only a small remark: The following code is valid in ConTeXt:
>
> \useURL [book-ns-openssl][http://www.amazon.com/exec/obidos/ASIN/059600270X/qid%3D1024342376/103-8123753-9606263][][Network
> Security with OpenSSL]
>
> but the syntax considers % like a comment mark, so I see another color
> for the text after %. It's possible to make the comment pattern
> smarter ? :)
Actually, yes, there is. Wait for me to get a new version sent upstream
to the Vim 7 CVS, add the following to your vimrc, and cheer:
let g:context_spacious_comments = 1
This will make it so that comments must be at the beginning of the line
or be preceded by a white-space,
nikolai
--
Nikolai Weibull: now available free of charge at http://bitwi.se/!
Born in Chicago, IL USA; currently residing in Gothenburg, Sweden.
main(){printf(&linux["\021%six\012\0"],(linux)["have"]+"fun"-97);}
prev parent reply other threads:[~2005-09-24 21:41 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-08 16:10 Mojca Miklavec
2005-07-08 17:48 ` Thomas A. Schmitz
2005-07-08 22:14 ` VnPenguin
2005-07-14 14:50 ` Christopher Creutzig
2005-07-14 16:16 ` Thomas A. Schmitz
2005-07-08 17:53 ` Hans Hagen
2005-07-08 21:32 ` Nikolai Weibull
2005-07-12 13:38 ` Mojca Miklavec
2005-07-08 21:28 ` Nikolai Weibull
2005-07-14 19:19 ` VnPenguin
2005-07-15 16:01 ` Nikolai Weibull
2005-09-24 21:41 ` Nikolai Weibull [this message]
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=20050924214121.GA8992@puritan.pnetwork \
--to=mailing-lists.context-users@rawuncut.elitemail.org \
--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).