[dev-context] Script files for third party modules.

Hans Hagen pragma at wxs.nl
Wed Jan 3 20:03:22 CET 2007


Mojca Miklavec wrote:
>> Ok. So for the time being, we will put 2context.vim in the same
>> directory as the module. Assuming that the module ends up somewhere in
>> tex/context/third/t-<whatever> kpsewhich will be able to find it.
>> Once, luatools become available, we may choose a different packaging
>> structure.
>>     
>
> That should also be OK. There's only one file anyway.
>
>   
>> To Mojca:
>> 1) What should we name the module? I was thinking t-syn-vim.tex,
>>     
>
> I'm OK with that name, but perhaps t-syntax-vim, I don't like
> shortcuts, syn could stand for just about anything.
>
>   
>> that way, if someone uses a different highlighting engine, say scite, that
>> module can be named t-syn-scite etc. (Hans, did you get the hint ;)
>>     
>
> If I'm/was thinking about the same thing as you are thinking ...
> .... then Hans will have to implement that anyway ;)
>
>   
yeah, since he has enough free time left anyway -) 

Hans 

-----------------------------------------------------------------
                                          Hans Hagen | PRAGMA ADE
              Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
     tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com
                                             | www.pragma-pod.nl
-----------------------------------------------------------------



More information about the dev-context mailing list