ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Aditya Mahajan <adityam@umich.edu>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Custom syntax highlighting
Date: Wed, 2 Mar 2016 09:45:54 -0500 (EST)	[thread overview]
Message-ID: <alpine.OSX.2.02.1603020939230.8080@nqv-znpobbx> (raw)
In-Reply-To: <nb699g$lml$1@ger.gmane.org>

On Wed, 2 Mar 2016, Nicola wrote:

> On 2016-03-02 02:14:33 +0000, Aditya Mahajan said:
>> 
>> I do not load the default vimrc, because that drastically slows down the
>> module.
>
> That makes sense. So, Vim is run with something like `vim -u NONE`, I 
> guess.

Yes. And if the vimrc option is used, then it is saved on file, and vim -u 
\vimrc_filename is run.

>>  Instead, there is an option to create a specific vimrc using:
>> 
>> \startvimrc[name=pgsql]
>> let g:sql_type_default='pgsql'
>> \stopvimrc
>> 
>> and then
>> 
>> \definevimtyping[SQL][..., vimrc=pgsql, ...]
>> 
>> By default, the script searches everything in `runtimepath`. If your 
> local
>> vim folder is not in runtimepath, you can set the runtimepath in the 
> vimrc
>> above.
>
> I had to set both runtimepath and nocompatible. Maybe this should be noted
> in the docs, or the module could run `vim -u NONE -N` (who needs compatible
> nowadays?). So, for future reference, this works:

I explicitly set compatible (but I don't remember why I did that anymore). 
This is the full command that is run:


\def\vimtyping@filter_command
   {vim -u \vimrc_filename\space % read global config file
         % --startuptime log
         % -V3log
        -X % dont connect to X server
        -i NONE % dont use viminfo file
        --noplugin % dont load plugins
        -e % run in ex mode
        -s % silent
        -C % set compatible
        -n % no swap file
        -c "syntax manual" % don't load filetype detection
        -c "set syntax=\externalfilterparameter\c!syntax" %
        -c "set tabstop=\externalfilterparameter\c!tab" %
        % vim only accepts 10 -c commands, so we combine a few let 
statements
        -c "let contextstartline=\externalfilterparameter\c!start 
\letterbar\space %
            let contextstopline=\externalfilterparameter\c!stop 
\letterbar\space %
            let 
strip=\getvalue{\vimtyping@id-\c!strip-\externalfilterparameter\c!strip}" 
%
        -c "let 
escapecomments=\getvalue{\vimtyping@id-\c!escape-\externalfilterparameter\c!escape}" 
%
        -c "let highlight=[\externalfilterparameter\c!highlight]" %
        \vimrc_extras\space
        -c "source \vimtyping@script_name" %
        -c "qa" %
        \externalfilterinputfile\space
        \externalfilteroutputfile}


I'll run my test suite with -N instead of -C. If everything works, I'll 
change to -N.

> \startvimrc[name=pgsql]
> set nocompatible
> set runtimepath+=~/.vim/bundle/pgsql
> let g:sql_type_default='pgsql'
> % ...
> \stopvimrc

I will add a note to the docs about runtimepath. When I wrote the module, 
bundle was not popular, but it is the default now.

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
___________________________________________________________________________________

  reply	other threads:[~2016-03-02 14:45 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-01 15:26 Nicola
2016-03-01 15:35 ` Aditya Mahajan
2016-03-01 18:14   ` Nicola
2016-03-02  2:14     ` Aditya Mahajan
2016-03-02  8:46       ` Nicola
2016-03-02 14:45         ` Aditya Mahajan [this message]
2016-03-02 15:23           ` Nicola
2016-03-02 11:06       ` Nicola
2016-03-02 11:20         ` Nicola
2016-03-02 18:21   ` Nicola
2016-03-02 19:34     ` Aditya Mahajan
2016-03-02 19:58       ` Nicola
2016-03-02 20:11         ` Aditya Mahajan
2016-03-02 20:29           ` Nicola
2016-03-01 21:53 ` Hans Hagen
2016-03-02  8:56   ` Nicola
2016-03-02  9:13     ` Hans Hagen
2016-03-02 10:45       ` Nicola
2016-03-02 23:16         ` Alan BRASLAU

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.OSX.2.02.1603020939230.8080@nqv-znpobbx \
    --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).