From: Aditya Mahajan <adityam@umich.edu>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: gVim complier plugin question
Date: Thu, 7 May 2009 11:23:56 -0400 (EDT) [thread overview]
Message-ID: <alpine.LNX.2.00.0905071122150.23064@ybpnyubfg.ybpnyqbznva> (raw)
In-Reply-To: <bc3554890905070815l72ed9cb7s23591c877f51d712@mail.gmail.com>
On Thu, 7 May 2009, Michael Bynum wrote:
> I was trying to get the context compiler plugin for gvim working, but
> I think I may be misunderstanding something about the instructions. I
> keep getting a "compiler not found" error when I try to set the
> compiler so I must have done something wrong.
>
> I downloaded the texexec.vim plugin from
> http://www.vim.org/scripts/script.php?script_id=1925 and copied it to
> /usr/share/vim/vim70/compiler/texexec.vim
> I then opened a context file with gvim and typed ":compiler=texexec"
> and I get "E666: compiler not supported: =texexec"
Sorry, that is a typo in the instructions. You should type
:compiler texexec
(without the = sign)
BTW, you might also be interested in syntax and indent files for ConTeXt
http://github.com/adityam/vim-context/tree/master
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 : https://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2009-05-07 15:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-07 15:15 Michael Bynum
2009-05-07 15:23 ` Aditya Mahajan [this message]
2009-05-07 16:25 ` Michael Bynum
2009-05-07 18:17 ` Aditya Mahajan
2009-05-07 19:17 ` Michael Bynum
2009-05-07 19:38 ` Aditya Mahajan
2009-05-07 20:22 ` Michael Bynum
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.00.0905071122150.23064@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).