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
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
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.nelson@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.nelson@gmail.com