From: Aditya Mahajan <adityam@umich.edu>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: vim syntax highlighting in MKIV
Date: Sat, 26 Jun 2010 22:38:35 -0400 (EDT) [thread overview]
Message-ID: <alpine.LNX.2.01.1006262226560.19991@ybpnyubfg.ybpnyqbznva> (raw)
In-Reply-To: <4C251E90.3050808@wxs.nl>
On Fri, 25 Jun 2010, Hans Hagen wrote:
> On 25-6-2010 9:48, Martin 'golodhrim' Scholz wrote:
>> Hi Hans, Mojca, Aditya and List,
>>
>> just tried to use the vim Syntax Highlighting module in ConTeXt MKIV, but
>> if running the documents complains it searches a file called
>>
>> filename-vimsyntax.tmp-vimsyntax.tmp
>>
>> sure that file not exists but there is a file called
>>
>> filename-vimsyntax.tmp
>>
>> is there a way to do a workaround so that the vim Syntaxhighlighting
>> module would work in MKIV or does it need to be rewriten completedly?
>
> probably something that M or A can fix easily
Something changed in mtxrun ...
Earlier (checked on the 2009.12.31) if I used
mtxrun bin:vim kpse:2context.vim
the "kpse:2context.vim" was expanded to the full path of 2context.vim.
Now (in 2010.06.20), "kpse:2context.vim" expands to "tree://<full-path>".
Of couse, vim does not understand the tree:// prefix and cannot load the
file. Is there an option to avoid the tree:// prefix?
Almost all the errors in t-vim over the years have due to trying to
support kpse: directive. (The errors were not a fault of ConTeXt, but the
way quotes are handled by cmd.exe and the various shells in *nix. I still
haven't figured out a syntax that works with all shells). This makes me
wonder whether it was a good idea to make vim module work out of the box.
Perhaps a more robust alternative was to ask the uses to copy 2context.vim
to $HOME/.vim/scripts/ and forget about getting mtxrun to locate the file.
What do others think?
Aditya
___________________________________________________________________________________
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:[~2010-06-27 2:38 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-25 19:48 Martin 'golodhrim' Scholz
2010-06-25 21:24 ` Hans Hagen
2010-06-27 2:38 ` Aditya Mahajan [this message]
2010-06-27 5:41 ` Aditya Mahajan
2010-06-27 10:04 ` Martin 'golodhrim' Scholz
2010-06-27 11:36 ` Peter Münster
2010-06-27 15:49 ` Aditya Mahajan
2010-06-27 18:16 ` Martin 'golodhrim' Scholz
2010-09-04 16:10 ` Chen Shen
2010-09-04 17:15 ` Wolfgang Schuster
2010-09-06 21:56 ` Aditya Mahajan
2010-06-27 12:02 ` Wolfgang Schuster
2010-06-27 15:47 ` 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=alpine.LNX.2.01.1006262226560.19991@ybpnyubfg.ybpnyqbznva \
--to=adityam@umich.edu \
--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).