From: Floris van Manen <vm@klankschap.nl>
Subject: Re[2]: getting context going
Date: Fri, 13 Aug 2004 01:32:48 +0200 [thread overview]
Message-ID: <112598324.20040813013248@klankschap.nl> (raw)
In-Reply-To: <411BE8DE.3020509@wxs.nl>
hans.
i re-started fresh (again :-) re-installing livetex using the
texsetup.exe command.
HH> if you install context, you can best do it into
HH>
HH> texmf-local
HH>
HH> (sometimes texmflocal)
HH>
HH> that way the files will be found there first; (it's also easier to prune
HH> that tree)
i did that too.
HH> if you have textools.rb:
HH>
HH> textools --fixtexmftrees
HH>
HH> will fix the tree
i did find textools.rb in the folder
C:\texlive\texmf-local\scripts\context\ruby
when i type the instruction windows does not (yet) understand it.
C:\>textools --fixtexmftrees
'textools' is not recognized as an internal or external command,
operable program or batch file.
in the windows environment there is:
path c:\texlive\bin\win32;...
texmfcnf c:\texlive\texmf-var\web2c
texmftemp c:\texlive\temp
texexec --verbose gives the following:
C:\>texexec --verbose
Kpathsea released!
TeXExec 4.0 - ConTeXt / PRAGMA ADE 1997-2003
current path : C:/Documents and Settings/vm/Desktop
locating ini file : found by kpsewhich
reading : c:/TeXLive/texmf/context/config/texexec.ini
setting : 'TeXShell' to 'fptex' for 'all'
setting : 'UsedInterfaces' to 'en nl metafun mptopdf' for 'all'
setting : 'UserInterface' to 'en' for 'all'
setting : 'TeXExecutable' to 'tex' for 'all'
setting : 'MpExecutable' to 'mpost' for 'all'
setting : 'MpToTeXExecutable' to 'mpto' for 'all'
setting : 'DviToMpExecutable' to 'dvitomp' for 'all'
setting : 'DviSpecialScript' to 'dvispec' for 'all'
setting : 'MpFormat' to 'metafun' for 'all'
setting : 'TeXFormatFlag' to '&' for 'all'
setting : 'MpFormatFlag' to '&' for 'all'
setting : 'TeXFontsPath' to 'l:/tex/texmf;l:/tex/texmf-local;' fo
r 'all'
setting : 'TeXHashExecutable' to 'mktexlsr' for 'fptex'
setting : 'TeXExecutable' to 'pdfetex' for 'fptex'
setting : 'TeXVirginFlag' to '-ini' for 'fptex'
setting : 'TeXPassString' to '-progname=context --default-transla
te-file=cp8bit' for 'fptex'
setting : 'TeXBatchFlag' to '-int=batchmode' for 'fptex'
setting : 'MpToTeXExecutable' to 'mpto' for 'fptex'
setting : 'MpVirginFlag' to '-ini' for 'fptex'
setting : 'MpPassString' to '-progname=mpost' for 'fptex'
setting : 'MpBatchFlag' to '-int=batchmode' for 'fptex'
used setting : TeXShell = fptex
used setting : SetupPath =
used setting : UserInterface = en
used setting : UsedInterfaces = en nl metafun mptopdf
used setting : TeXFontsPath = l:/tex/texmf;l:/tex/texmf-local;
used setting : MpExecutable = mpost
used setting : MpToTeXExecutable = mpto
used setting : DviToMpExecutable = dvitomp
used setting : TeXProgramPath =
used setting : TeXFormatPath =
used setting : ConTeXtPath =
used setting : TeXScriptsPath =
used setting : TeXHashExecutable = mktexlsr
used setting : TeXExecutable = pdfetex
used setting : TeXVirginFlag = -ini
used setting : TeXBatchFlag = -int=batchmode
used setting : TeXNonStopFlag = -int=nonstopmode
used setting : MpBatchFlag = -int=batchmode
used setting : MpNonStopFlag = -int=nonstopmode
used setting : TeXPassString = -progname=context --default-translate-f
ile=cp8bit
used setting : TeXFormatFlag = &
used setting : MpFormatFlag = &
used setting : MpVirginFlag = -ini
used setting : MpPassString = -progname=mpost
used setting : MpFormat = metafun
used setting : MpFormatPath =
used setting : FmtLanguage =
used setting : FmtBodyFont =
used setting : FmtResponse =
used setting : TcXPath =
used setting : SetFile =
applications will use : c:\TeXLive\texmf-var\web2c/texmf.cnf
locating fmtutil : C:/TeXLive/bin/win32/fmtutil.exe
--help overview of all options and their values
--help all all about all options
--help short just the main options
--help mode ... pdf all about a few options
--help '*.pdf' all about options containing 'pdf'
total run time : 0 seconds
the problem to me is that it is difficult to know what to look for and
where. then it turns out that the documentation is not in sync with
reality. that makes it difficult for a novice user (which i try to
remain :-).
i'm really looking forward in using context, but getting the car out
of the garage is cumbersome.
which (automatic) setup is best to use for XP and OSX ?
as i wrote before, i hope at least that there is also a positive
aspect to my stumbling e.g. what do people wrong...
% floris
next prev parent reply other threads:[~2004-08-12 23:32 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-10 17:30 Some problems with framing typed text Brooks Moses
2004-08-10 18:00 ` Henning Hraban Ramm
2004-08-10 18:47 ` Brooks Moses
2004-08-10 19:04 ` Hans Hagen
2004-08-10 20:35 ` no graph after compilation Floris van Manen
2004-08-11 12:55 ` Peter Rolf
2004-08-11 13:38 ` Re[2]: " Floris van Manen
2004-08-11 14:00 ` Vit Zyka
2004-08-11 14:09 ` Re[2]: " Floris van Manen
2004-08-11 14:21 ` Patrick Gundlach
2004-08-11 14:44 ` Re[2]: " Floris van Manen
2004-08-11 15:07 ` Patrick Gundlach
2004-08-11 15:14 ` Patrick Gundlach
2004-08-11 15:24 ` Re[2]: " Floris van Manen
2004-08-11 15:34 ` Patrick Gundlach
2004-08-11 15:57 ` Re[2]: " Floris van Manen
2004-08-11 16:38 ` Patrick Gundlach
2004-08-11 18:03 ` Re[2]: " Floris van Manen
2004-08-11 18:17 ` Patrick Gundlach
2004-08-11 22:17 ` Re[2]: " Floris van Manen
2004-08-12 7:47 ` Patrick Gundlach
2004-08-12 8:05 ` Eros Albertazzi
2004-08-12 11:30 ` Re[2]: " Floris van Manen
2004-08-12 11:03 ` Vit Zyka
2004-08-12 11:29 ` Re[2]: " Floris van Manen
2004-08-12 19:26 ` Patrick Gundlach
2004-08-12 22:02 ` Hans Hagen
2004-08-12 23:32 ` Floris van Manen [this message]
2004-08-12 23:48 ` getting context going Hans Hagen
2004-08-13 8:24 ` Patrick Gundlach
2004-08-13 12:29 ` Re[2]: getting context going --> feature tool request Floris van Manen
2004-08-12 7:25 ` no graph after compilation Hans Hagen
2004-08-12 11:06 ` Re[2]: " Floris van Manen
2004-08-12 7:13 ` Hans Hagen
2004-08-12 7:42 ` Patrick Gundlach
2004-08-11 16:00 ` Vit Zyka
2004-08-11 16:30 ` Patrick Gundlach
2004-08-11 17:14 ` Re[2]: " Peter Münster
2004-08-10 18:48 ` Some problems with framing typed text Hans Hagen
2004-08-10 19:21 ` Brooks Moses
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=112598324.20040813013248@klankschap.nl \
--to=vm@klankschap.nl \
--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).