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

Hans Hagen pragma at wxs.nl
Wed Jan 3 17:01:37 CET 2007


Aditya Mahajan wrote:
>
>>> What is the correct way of finding something in the texmf-tree but 
>>> outside program space 'context'?
>>>
>>>       
>> --program=yourtex
>>     
>
> what should yourtex be in this case?
>   
dunno, depends on the texmf.cnf file
>   
>> but i wonder, isn't the vim stuff in the context tree? can kpse find it?
>>     
>
> Aparantly not. Something seems to be broken.
>
>         kpsewhich --version
>         kpathsea version
>         Copyright 2005 Karl Berry & Olaf Weber.
>         There is NO warranty.  You may redistribute this software
>         under the terms of the GNU General Public License.
>         For more information about these matters, see the files named
>         GPL and LGPL.
>
> Notice no version number!
>   
ancient ; and no warranty either
>      kpsewhich texexec.rb
>
> does not give anything.
>
>     kpsewhich --debug=10 texexec.rb
>
> gives
>    ...[lots of lines]
>    ...[ending with repeats of]
>    kdebug:hash_shared_lookup(texexec.rb.tex) => (nil)
>    kdebug:hash_shared_lookup(texexec.rb) =>
>    e:\isoimage\usr\local\context\tex\texmf-local/scripts/context/ruby/
>    e:\isoimage\usr\local\context\tex\texmf-local/scripts/context/ruby/
>
> Notice that the complete path is not output. That is compare from
>
>    kpsewhich --debug=10 core-ver.tex
>
> which gives
>    ...[lots of lines]
>    kdebug:hash_shared_lookup(core-ver.tex) =>
>    e:\isoimage\usr\local\context\tex\texmf-local/tex/context/base/
>    e:\isoimage\usr\local\context\tex\texmf-local/tex/context/base/
>    kdebug:hash_shared_lookup(core-ver.tex) =>
>    e:\isoimage\usr\local\context\tex\texmf-local/tex/context/base/
>    e:\isoimage\usr\local\context\tex\texmf-local/tex/context/base/
>    e:\isoimage\usr\local\context\tex\texmf-local/tex/context/base/core-ver.tex
>
> The last line is the location of the file, which is output to stdout. 
> So even though kpsewhich is able to find the file in scripts/, it does 
> not give any output. I do not know what is happening here. Is there a 
> bug in kpsewhich? The binaries are from context stand alone 
> distribution overwritten by pdftex-1.40.0-beta-20060213 binaries (I do 
> not know where the kpsewhich binary came from, context stand alone or 
> pdftex).
>
>   
maybe the scripts path in texmf.cnf has no \\ appended (recurse)


anyhow, maybe it's about time to kick out kpsewhich and use luatools 
which is faster too and more clever

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