OK, I just realized that the pdftex "Tex Live 2010" actually is the
pdftex in the current context beta...

peter@computer:~$ which pdftex
/home/peter/context1220/tex/texmf-linux/bin/pdftex

peter@computer:~$ pdftex -v
pdfTeX 3.1415926-1.40.11-2.2 (TeX Live 2010)
kpathsea version 6.0.0
Copyright 2010 Peter Breitenlohner (eTeX)/Han The Thanh (pdfTeX).
There is NO warranty.  Redistribution of this software is
covered by the terms of both the pdfTeX copyright and
the Lesser GNU General Public License.
For more information about these matters, see the file
named COPYING and the pdfTeX source.
Primary author of pdfTeX: Peter Breitenlohner (eTeX)/Han The Thanh (pdfTeX).
Compiled with libpng 1.2.40; using libpng 1.2.40
Compiled with zlib 1.2.3; using zlib 1.2.3
Compiled with xpdf version 3.02pl4

so the problem is really just mkii vs. mkiv.


On Tue, Jan 3, 2012 at 2:07 PM, Peter Park Nelson
<peter.park.nel...@gmail.com> wrote:
> Thanks for your responses. I should have specified that I am using
> Linux (Ubuntu). I don't have any previous SciTE configuration files in
> my home directory.
>
> I used the instructions from contextgarden and
> scite-context-readme.pdf, including creating a launch script that sets
> the PATH to include my context standalone binary. What I don't
> understand now is that SciTE finds the correct standalone binary but
> uses texexec to run mkii instead of mkiv as is supposed to be the
> defuault:
>
> ConTeXt  ver: 2011.12.31 15:44 MKII
>
> and calls an old pdftex from a separate TexLive installation:
>
> This is pdfTeX, Version 3.1415926-1.40.11 (TeX Live 2010)
>
> Any suggestions?
> Thanks.
>
>>texexec --pdf H1.tex
> /home/peter/context1220/tex/texmf-context/scripts/context/ruby/base/system.rb:16:
> warning: Insecure world writable dir /usr/local/texlive in PATH, mode
> 040777
> TeXExec | processing document 'H1.tex'
> TeXExec | no ctx file found
> TeXExec | tex processing method: context
> TeXExec | TeX run 1
> TeXExec | writing option file H1.top
> TeXExec | using randomseed 1125
> TeXExec | tex engine: pdftex
> TeXExec | tex format: cont-en.mkii
> warning: Could not open char translation file `natural.tcx'.
> This is pdfTeX, Version 3.1415926-1.40.11 (TeX Live 2010)
>  \write18 enabled.
> entering extended mode
> (./H1.tex
>
> ConTeXt  ver: 2011.12.31 15:44 MKII  fmt: 2011.12.31  int: english/english
>
> system          : cont-new.mkii loaded
> (/home/peter/context1220/tex/texmf-context/tex/context/base/cont-new.mkii
> systems         : beware: some patches loaded from cont-new.mkii
> )
> system          : cont-sys.rme loaded
> (/home/peter/context1220/tex/texmf-context/tex/context/user/cont-sys.rme
> (/home/peter/context1220/tex/texmf-context/tex/context/base/type-siz.mkii)
> (/home/peter/context1220/tex/texmf-context/tex/context/base/type-one.mkii))
> system          : H1.top loaded
> (./H1.top)
>
> On Tue, Jan 3, 2012 at 9:58 AM, John Kitzmiller <jki...@gmail.com> wrote:
>> It looks like you need to point Scite to
>> /home/peter/context1220/texmf-mswin/bin (assuming you are using
>> windows) in your PATH.
>>
>>
>>
>> On Mon, Jan 2, 2012 at 10:52 PM, Peter Park Nelson
>> <peter.park.nel...@gmail.com> wrote:
>>>
>>> Hello, I installed and configured SciTE today to try it out. I am
>>> using the standalone distribution. When I try to process a context
>>> document with F7, SciTE calls texexec and uses mkii instead of mkiv (I
>>> always use mkiv/luatex). How do I configure SciTE to use mkiv?
>>>
>>> Here's the beginning of the output:
>>>
>>> >texexec --pdf H1.tex
>>> /home/peter/context1220/tex/texmf-context/scripts/context/ruby/base/system.rb:16:
>>> warning: Insecure world writable dir /usr/local/texlive in PATH, mode
>>> 040777
>>> TeXExec | processing document 'H1.tex'
>>> TeXExec | no ctx file found
>>> TeXExec | tex processing method: context
>>> TeXExec | TeX run 1
>>> TeXExec | writing option file H1.top
>>> TeXExec | using randomseed 202
>>> TeXExec | tex engine: pdftex
>>> TeXExec | tex format: cont-en.mkii
>>> warning: Could not open char translation file `natural.tcx'.
>>> This is pdfTeX, Version 3.1415926-1.40.11 (TeX Live 2010)
>>>  \write18 enabled.
>>> entering extended mode
>>> (./H1.tex
>>>
>>> ConTeXt  ver: 2011.12.31 15:44 MKII  fmt: 2011.12.31  int: english/english
>>>
>>> system          : cont-new.mkii loaded
>>> (/home/peter/context1220/tex/texmf-context/tex/context/base/cont-new.mkii
>>>
>>> [...more output...]
>>> --
>>> Peter Park Nelson
>>> peter.park.nel...@gmail.com
>>> ___________________________________________________________________________________
>>> 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
>>> ___________________________________________________________________________________
>> ___________________________________________________________________________________
>> 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
>> ___________________________________________________________________________________
>
>
>
> --
> Peter Park Nelson
> peter.park.nel...@gmail.com



-- 
Peter Park Nelson
peter.park.nel...@gmail.com
___________________________________________________________________________________
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 via email to