From: John Kitzmiller <jkitzm@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: SciTE configuration to use mkiv instead of mkii
Date: Tue, 3 Jan 2012 10:58:23 -0500 [thread overview]
Message-ID: <CAHYz2AV6Z1sonNhrj950s2dN8Tc6ofnoPHb3fENNRs7075XYNw@mail.gmail.com> (raw)
In-Reply-To: <CAGfkPGkfFQe6OhREVhf7Qm8PrJyaNFZu=3Qk_1BZLYY+Kumyhg@mail.gmail.com>
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.nelson@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.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
___________________________________________________________________________________
next prev parent reply other threads:[~2012-01-03 15:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-03 3:52 Peter Park Nelson
2012-01-03 8:31 ` Hans Hagen
2012-01-03 10:25 ` Mari Voipio
2012-01-03 15:58 ` John Kitzmiller [this message]
2012-01-03 20:07 ` Peter Park Nelson
2012-01-03 22:57 ` Peter Park Nelson
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=CAHYz2AV6Z1sonNhrj950s2dN8Tc6ofnoPHb3fENNRs7075XYNw@mail.gmail.com \
--to=jkitzm@gmail.com \
--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).