New Beta

New Beta

[David Arnold]

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="us-ascii", Size: 1099 bytes --]

All,

I don't have the very latest Miktex, but a reasonably new one (Miktex 2
with Update 1). I unpacked the new Context beta (texexec.ini attached) and
used Miktex Options->Tex Formats to build formats for pdfelatex and
pdfetex, refreshing the filename database whenever I could.

texexec --make

seemed to go well (I have the eformats in \localtexmf\miktex\fmt. But when
I compile this sample file,

\starttext \framed {Let’s see if it works.} \stoptext

I got this error message:

F:\ConTeXt\MyWork>texexec junk

 TeXExec 2.5 - ConTeXt / PRAGMA ADE 1997-2001

            executable : pdfetex
                format : f:/localtexmf/miktex/fmt/cont-en
             inputfile : junk
                output : standard
             interface : en
          current mode : all
               TeX run : 1

This is pdfeTeX, Version 3.14159-14f-released-20000525-2.1 (MiKTeX 2 UP 1)
initexmf: don't know how to dump miktex
cannot make f:/localtexmf/miktex.efmt
I can't find the default format file!

              run time : 1 seconds

Has anyone experienced this before and know how to cure the problem?

[-- Attachment #2: texexec.ini --]
[-- Type: text/plain, Size: 4590 bytes --]

% == introduction ==
%
% This is 'texexec.ini', the file used by texexec to determine where
% to find files, what TeX to use, what flags to pass, etc. Although
% TeXexec tries to locate things itself, a little help is sometimes
% needed. One can influence texexec by setting some variables. These
% are only needed when the automatic determined settings fail.
%
% == interfacing ==
%
% UsedInterfaces  nl,en  the formats generated with --make
% UserInterface   nl     the default format used
%
% == binaries ==
%
% TeXExecutable      pdfetex  the TeX binary to use
% MpExecutable       mpost    the MetaPost binary to use
% MpToTeXExecutable  mpto     the MetaPost to TeX converter
% DviToMpExecutable  dvitomp  the DVI to MetaPost converter
%
% == Scripts ==
%
% DviSpecialScript   dvispec  the DVI special filter script
%
% == flags ==
%
% TeXFormatFlag  &     the format introducer
% TeXVirginFlag  -ini  the format generation switch
%
% == paths ==
%
set TeXFormatPath   to f:/localtexmf/miktex/fmt
set ConTeXtPath     to f:/Miktex/tex/context/base
set SetupPath       to f:/Miktex/tex/context/base
set TeXScriptsPath  to f:/Miktex/context/perltk
% TeXFontsPath    texmf                   font files
%
% == the main shell setting ==
%
% As shown below, one can define his/her own sections. We default to
% the teTeX/fpTeX web2c based settings.

%set  TeXShell  to  tetex
%set TeXShell  to  fptex
set TeXShell  to  miktex
%set TeXShell  to  private

% == setting up the variables ==
%
% Here are some general defaults. They can be overruled later.

set  UsedInterfaces     to  en nl de uk
set  UserInterface      to  en

set  TeXExecutable      to  tex

set  MpExecutable       to  mpost
set  MpToTeXExecutable  to  mpto
set  DviToMpExecutable  to  dvitomp
set  DviSpecialScript   to  dvispec

set  MpFormat           to  metafun

set  TeXFormatFlag      to  &
set  MpFormatFlag       to  &

%set  TeXFontsPath       to  l:/tex/texmf;l:/tex/texmf-local;

% For teTeX the next settings will do.

for  tetex  set  TeXExecutable     to  pdfetex
for  tetex  set  TeXVirginFlag     to  -ini
for  tetex  set  TeXPassString     to  -progname=context
for  tetex  set  TeXBatchFlag      to  -int=batchmode
for  tetex  set  MpToTeXExecutable to  mpto
for  tetex  set  MpVirginFlag      to  -ini
for  tetex  set  MpPassString      to  -progname=mpost
for  tetex  set  MpBatchFlag       to  -int=batchmode

% These also apply to fpTeX.

for  fptex  set  TeXExecutable     to  pdfetex
for  fptex  set  TeXVirginFlag     to  -ini
for  fptex  set  TeXPassString     to  -progname=context
for  fptex  set  TeXBatchFlag      to  -int=batchmode
for  fptex  set  MpToTeXExecutable to  mpto
for  fptex  set  MpVirginFlag      to  -ini
for  fptex  set  MpPassString      to  -progname=mpost
for  fptex  set  MpBatchFlag       to  -int=batchmode

% MikTeX users probably have to set up some paths too.

for  miktex  set  TeXExecutable     to  pdfetex
for  miktex  set  TeXVirginFlag     to  --initialize
for  miktex  set  TeXBatchFlag      to  --interaction=batchmode
for  miktex  set  MpToTeXExecutable to  mptotex
for  miktex  set  MpVirginFlag      to  --initialize
for  miktex  set  MpPassString      to
for  miktex  set  MpBatchFlag       to  --interaction=batchmode
for  miktex  set  TeXFormatFlag     to  --undump=
for  miktex  set  MpFormatFlag      to  --undump=

% These are the settings used on some machines at PRAGMA ADE that
% don't use the texmf tree. They can serve as an example for local
% settings. Local settings should either be added to the previous
% one, or go without the 'for' directives. Consider these
% settings as an example.

for  private  set  UsedInterfaces  to  en nl
for  private  set  UserInterface   to  nl
for  private  set  ConTeXtPath     to  t:/sources/
for  private  set  SetupPath       to  t:/perl/
for  private  set  TeXScriptsPath  to  t:/perl/

% == read this too ==
%
% If this file is called 'texexec.rme', copy it to 'texexec.ini',
% check the settings above, change them according to your TeX
% distribution, and say:
%
%   texexec  --verbose
%
% When set up properly, you should see your local settings fly by.
% When these settings are ok, the next call should work:
%
%   texexec  --make
%
% and you should be able to process a file by saying
%
%   texexec  filename
%
% See 'mtexexec.pdf' for more information on the flags you can use with
% 'texexec'. Also make sure you have the 'texutil' script installed in
% the same path as 'texexec'.

% Experimental
%
% set  TcXPath     to  d:/tex/texmf/web2c
% set  FmtLanguage to  pl
% set  FmtBodyFont to  plr

Re: New Beta

[Hans Hagen]

At 06:02 PM 8/20/2001 -0700, David Arnold wrote:

>                 format : f:/localtexmf/miktex/fmt/cont-en

>This is pdfeTeX, Version 3.14159-14f-released-20000525-2.1 (MiKTeX 2 UP 1)
>initexmf: don't know how to dump miktex
>cannot make f:/localtexmf/miktex.efmt

strange, since there is nothing to dump or make in this stage, are you sure 
you don't run inimiktex or so

>I can't find the default format file!
>
>               run time : 1 seconds

at least it runs fast,

Hans
-------------------------------------------------------------------------
                                   Hans Hagen | PRAGMA ADE | pragma@wxs.nl
                       Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
  tel: +31 (0)38 477 53 69 | fax: +31 (0)38 477 53 74 | www.pragma-ade.com
-------------------------------------------------------------------------

Re: New Beta

[Olya Briginets]

Hello David,

David Arnold wrote:

[skipped]

> This is pdfeTeX, Version 3.14159-14f-released-20000525-2.1 (MiKTeX 2 UP 1)
> initexmf: don't know how to dump miktex
> cannot make f:/localtexmf/miktex.efmt
> I can't find the default format file!
> 
>               run time : 1 seconds
> 
> Has anyone experienced this before and know how to cure the problem?

I have found that this is not texexec but solely MiKTeX problem, the problem
is that it seems that MiKTeX accept only restricted lenght of its arguments and
cuts off the rest of argument for each of arguments separately, so if your
TeXFormatPath contains f:/LocalTeXMF/miktex/fmt, then command line argument
--undump=f:/LocalTeXMF/miktex/fmt/cont-en are cut after /miktex, so TeX think
you wish to use miktex.efmt, not cont-en.efmt. Once you changed --undump= to &,
command line are shorter and ain't cut off. I don't know whether it's fixed in
MiKTeX 2.1.

Olya

Re: New Beta

[Hans Hagen]

At 11:31 AM 8/24/2001 +0300, Olya Briginets wrote:

>I have found that this is not texexec but solely MiKTeX problem, the problem
>is that it seems that MiKTeX accept only restricted lenght of its 
>arguments and
>cuts off the rest of argument for each of arguments separately, so if your
>TeXFormatPath contains f:/LocalTeXMF/miktex/fmt, then command line argument
>--undump=f:/LocalTeXMF/miktex/fmt/cont-en are cut after /miktex, so TeX think
>you wish to use miktex.efmt, not cont-en.efmt. Once you changed --undump= 
>to &,
>command line are shorter and ain't cut off. I don't know whether it's fixed in
>MiKTeX 2.1.

Impressive analysis! I'm sure that david will communicate this with the 
miktex people.

Hans
-------------------------------------------------------------------------
                                   Hans Hagen | PRAGMA ADE | pragma@wxs.nl
                       Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
  tel: +31 (0)38 477 53 69 | fax: +31 (0)38 477 53 74 | www.pragma-ade.com
-------------------------------------------------------------------------

Re[2]: New Beta

[Giuseppe Bilotta]

OB> I have found that this is not texexec but solely MiKTeX problem, the problem
OB> is that it seems that MiKTeX accept only restricted lenght of its arguments and
OB> cuts off the rest of argument for each of arguments separately, so if your
OB> TeXFormatPath contains f:/LocalTeXMF/miktex/fmt, then command line argument
OB> --undump=f:/LocalTeXMF/miktex/fmt/cont-en are cut after /miktex, so TeX think
OB> you wish to use miktex.efmt, not cont-en.efmt. Once you changed --undump= to &,
OB> command line are shorter and ain't cut off. I don't know whether it's fixed in
OB> MiKTeX 2.1.

Is it necessary to use TeXFormatPath? I let MiKTeX find the corred
path (or rather put the format files in the default path ...)

Re[2]: New Beta

[Hans Hagen]

At 04:14 PM 8/24/2001 +0200, Giuseppe Bilotta wrote:

>OB> I have found that this is not texexec but solely MiKTeX problem, the 
>problem
>OB> is that it seems that MiKTeX accept only restricted lenght of its 
>arguments and
>OB> cuts off the rest of argument for each of arguments separately, so if your
>OB> TeXFormatPath contains f:/LocalTeXMF/miktex/fmt, then command line 
>argument
>OB> --undump=f:/LocalTeXMF/miktex/fmt/cont-en are cut after /miktex, so 
>TeX think
>OB> you wish to use miktex.efmt, not cont-en.efmt. Once you changed 
>--undump= to &,
>OB> command line are shorter and ain't cut off. I don't know whether it's 
>fixed in
>OB> MiKTeX 2.1.
>
>Is it necessary to use TeXFormatPath? I let MiKTeX find the corred
>path (or rather put the format files in the default path ...)

it depends on how many texmf trees you use: here i have a couple -)

but, you can of course let miktex sort things out since on windows there is 
less chance on write permission problems

Hans
-------------------------------------------------------------------------
                                   Hans Hagen | PRAGMA ADE | pragma@wxs.nl
                       Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
  tel: +31 (0)38 477 53 69 | fax: +31 (0)38 477 53 74 | www.pragma-ade.com
-------------------------------------------------------------------------

Re[2]: new beta

[Hans Hagen]

At 12:38 PM 12/1/2002 +0100, you wrote:

>Ok I found it ... manually: the link from the "Beta downloads"
>page still points to the nonbeta version.

hm, persistent bug in a perl script -) will repair it

Hans
-------------------------------------------------------------------------
                                   Hans Hagen | PRAGMA ADE | pragma@wxs.nl
                       Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
  tel: +31 (0)38 477 53 69 | fax: +31 (0)38 477 53 74 | www.pragma-ade.com
-------------------------------------------------------------------------
                        information: http://www.pragma-ade.com/roadmap.pdf
                     documentation: http://www.pragma-ade.com/showcase.pdf
-------------------------------------------------------------------------

Re[2]: new beta

[Giuseppe Bilotta]

Sunday, December 1, 2002 Giuseppe Bilotta wrote:


GB> Sunday, December 1, 2002 Hans Hagen wrote:

HH>> Hi,

HH>> I uploaded a new beta.

GB> Can't seem to find it ...

Ok I found it ... manually: the link from the "Beta downloads"
page still points to the nonbeta version.

-- 
Giuseppe "Oblomov" Bilotta

Re: Re[2]: New Beta

[Hans Hagen]

At 09:14 AM 8/24/2001 -0700, David Arnold wrote:

>However, this is new to Miktex 2, and traditionally I have always followed
>the following steps:
>
>1. Download and extract the new Context beta from Pragma.
>2. Set environment variables in texexec.rme and rename to texexec.ini.
>3. Rename cont-sys.rme to cont-sys.tex.
>
>Actually, in 2 and 3, I usually just adjust my old texexec.ini and
>cont-sys.tex.

i think that this is not needed, unless there is a big change in texexec; 
you only need to move the pl files to the right path [unless you have 
context/perltk in your path]

the cont-sys.tex file is never part o fthe zip, so you can leave your local 
copy untouched [actually, it should be undec /tex/context/usr so that you 
can safely delete the base path] Of course it's always a good idea to look 
into cont-sys.rme esp now, since some font defaults go there, but in a 
while it will stabelize

>4. Run texexec --verbose to see if setting look good.

ok

>5. Run texexec --make to build the formats. Because the TeXFormatPath is
>set in texexec.ini, the formats are created AND moved into the correct
>place in my /localtexmf/miktex/fmt.

>6. Then I run
>
>texexec --make --alone metafun

no --alone needed there since fmtutil does not support mem's at all

>This builds metafun.mem. Unfortunately, there is no environment variable I
>have found yet in texexec.ini that will move this automatically to the
>correct spot in my miktex distribution, so I must manually move metafun.mem
>to \localtexmf\miktex\mem.

hm. there are three ways to set the path: automatically (kpsewhich), 
manually (env var) or in the ini file and i now see that the last one is 
not supported for mp. I've added it and let it default to TeXFormatPath so 
you don't need to change / add something.

>7. Then I run
>
>texexec --make --alone --format=mptopdf

texexec --make --alone mptopdf

will do too, i'll also make that one alone by default

>This places mptopdf.efmt in /locatexmf/miktex/fmt. Then I take runperl.exe
>and rename it to mptopdf.exe. These all used to be in
>\miktex\context\perltk, but Christian has moved texexec.exe into the
>\miktex\miktex\bin directory, which is on the path created when Miktex is
>installed. This is a cool piece of software which allows me to type
>
>mptopdf filename.1
>
>where filename.1 is Metapost output. The result is the file filename-1.pdf.
>Nice, huh? The command also accepts wildcards, as in
>
>mptopdf filename.? or mptopdf filename.*
>
>Old habits die hard, so I'm not quite sure how I want to setup my new
>Miktex, but I am learning.

never change old habits when they are ok, so let me fix things that are 
broken instead -)

Hans
-------------------------------------------------------------------------
                                   Hans Hagen | PRAGMA ADE | pragma@wxs.nl
                       Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
  tel: +31 (0)38 477 53 69 | fax: +31 (0)38 477 53 74 | www.pragma-ade.com
-------------------------------------------------------------------------

Re: Re[2]: New Beta

[David Arnold]

Giuseppe,

This is a good question. There is a Miktex Options, upon which is a Tab for
TeX formats, where one can setup and build formats.

However, this is new to Miktex 2, and traditionally I have always followed
the following steps:

1. Download and extract the new Context beta from Pragma.
2. Set environment variables in texexec.rme and rename to texexec.ini.
3. Rename cont-sys.rme to cont-sys.tex.

Actually, in 2 and 3, I usually just adjust my old texexec.ini and
cont-sys.tex.

4. Run texexec --verbose to see if setting look good.

5. Run texexec --make to build the formats. Because the TeXFormatPath is
set in texexec.ini, the formats are created AND moved into the correct
place in my /localtexmf/miktex/fmt.

6. Then I run 

texexec --make --alone metafun

This builds metafun.mem. Unfortunately, there is no environment variable I
have found yet in texexec.ini that will move this automatically to the
correct spot in my miktex distribution, so I must manually move metafun.mem
to \localtexmf\miktex\mem.

7. Then I run

texexec --make --alone --format=mptopdf

This places mptopdf.efmt in /locatexmf/miktex/fmt. Then I take runperl.exe
and rename it to mptopdf.exe. These all used to be in
\miktex\context\perltk, but Christian has moved texexec.exe into the
\miktex\miktex\bin directory, which is on the path created when Miktex is
installed. This is a cool piece of software which allows me to type

mptopdf filename.1

where filename.1 is Metapost output. The result is the file filename-1.pdf.
Nice, huh? The command also accepts wildcards, as in

mptopdf filename.? or mptopdf filename.*

Old habits die hard, so I'm not quite sure how I want to setup my new
Miktex, but I am learning.

At 04:14 PM 8/24/01 +0200, you wrote:
>
>OB> I have found that this is not texexec but solely MiKTeX problem, the
problem
>OB> is that it seems that MiKTeX accept only restricted lenght of its
arguments and
>OB> cuts off the rest of argument for each of arguments separately, so if
your
>OB> TeXFormatPath contains f:/LocalTeXMF/miktex/fmt, then command line
argument
>OB> --undump=f:/LocalTeXMF/miktex/fmt/cont-en are cut after /miktex, so
TeX think
>OB> you wish to use miktex.efmt, not cont-en.efmt. Once you changed
--undump= to &,
>OB> command line are shorter and ain't cut off. I don't know whether it's
fixed in
>OB> MiKTeX 2.1.
>
>Is it necessary to use TeXFormatPath? I let MiKTeX find the corred
>path (or rather put the format files in the default path ...)
>
>