Additional steps taken since the first e-mail

Additional steps taken since the first e-mail

[Mats Broberg]

Listmembers,

I have also done the following since the first e-mail:


- Copied the contents of "texexec.rme" to "texexec.ini"

- Uncommented the "set TeXShell to miktex" line in the new "texexec.ini"
file.

- Added the string "C:\texmf\miktex\context\perltk" to the PATH
(however, there is no "context" or "perltk" folder in the "miktex"
folder. Shouldn't there be?)


However, the problem still persists.

Best regards,
Mats Broberg

Re: Additional steps taken since the first e-mail

[Matthew Huggett]

Mats Broberg wrote:
>   I have also done the following since the first e-mail:
>
>
>   - Copied the contents of "texexec.rme" to "texexec.ini"

OK


>   - Uncommented the "set TeXShell to miktex" line in the new "texexec.ini"
>   file.
>
>   - Added the string "C:\texmf\miktex\context\perltk" to the PATH
>   (however, there is no "context" or "perltk" folder in the "miktex"
>   folder. Shouldn't there be?)

As far as I remember, apart from installing Perl (ActivePerl) and
adding it to PATH, I only had to add MikTeX's bin directory to
PATH.

Have you also generated the formats?  From texexec.rme:

,----
| % 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
`----

And then of course, be sure to run:

,----
| mktexlsr
`----

Regarding the files not having line breaks, I made the same mistake
when I started using ConTeXt.  The files have Unix end of line
characters, so Notepad and other Windows-only editors will just give
you a long string of garbage, as you discovered.  Hans has put a lot
of work in making Scite work nicely with ConTeXt, so you might find
that helpful.  Other users have their favorites (Emacs, jEdit, etc.).

Good luck,

Matthew

RE: Additional steps taken since the first e-mail

[Mats Broberg]

Dear all,

OK, as Matthew suggested (thx!), I ran "texexec --make", which returned
alot of text flying by my command line window. Then I ran my test file
again, and it created a dvi file (as well as 6 other files. So it seems
to work now.

However, when I run the test file, I still get the "unknown file type:
texmfscripts" as the first entry, but the test file seem to be processed
anyway. Does this mean I can forget about this warning?

Also, what does "mktexlsr" refer to, that Matthew mentions below? In the
"texexec.ini" file it is mentioned in relation to fptex and tetex, but
for miktex the corresponding line says:

for  miktex  set  TeXHashExecutable to  initexmf --update-fndb

Best regards,
Mats Broberg

Matthew Huggett wrote

> Have you also generated the formats?  From texexec.rme:
> 
> ,----
> | % 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
> `----
> 
> And then of course, be sure to run:
> 
> ,----
> | mktexlsr
> `----

Re: Additional steps taken since the first e-mail

[Matthew Huggett]

>   Also, what does "mktexlsr" refer to

I don't know how it really works, so I can only explain this in
layman's terms.  If you look in your texmf directory, you should see a
ls-R file.  If you have a texmf-local tree, there should be one there
too.  These ls-R files make up a database that are used to locate
various files in a TeX system.  After you make changes, like updating
and rebuilding formats, or copying texexec.rme to texexec.ini, you
need to update the databases before TeX becomes aware of the changes.
This is what mktexlsr does.  On some systems, the command might be
"texhash".


Matthew

Re: Additional steps taken since the first e-mail

[h h extern]

Mats Broberg wrote:

> However, when I run the test file, I still get the "unknown file type:
> texmfscripts" as the first entry, but the test file seem to be processed
> anyway. Does this mean I can forget about this warning?

seesm like your tex binaries and context scripts are not in sync;

> Also, what does "mktexlsr" refer to, that Matthew mentions below? In the
> "texexec.ini" file it is mentioned in relation to fptex and tetex, but
> for miktex the corresponding line says:
> 
> for  miktex  set  TeXHashExecutable to  initexmf --update-fndb

miktex and web2c have a different filename databases, but miktex has kpsewhich 
bundled so it can work with apps that depend on that


Hans

-----------------------------------------------------------------
                                           Hans Hagen | PRAGMA ADE
               Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
      tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com
                                              | www.pragma-pod.nl
-----------------------------------------------------------------

RE: Additional steps taken since the first e-mail

[Mats Broberg]

Hans,

OK, and what should I do to remedy this? I am using ConTeXt out of the
box, as it is when you install MikTeX. 

Should I download something else from your site? A more recent
distribution?

My log says: ConTeXt  ver: 2005.01.24

Best regards,
Mats Broberg

On Behalf Of h h extern

> > However, when I run the test file, I still get the "unknown 
> file type: 
> > texmfscripts" as the first entry, but the test file seem to be 
> > processed anyway. Does this mean I can forget about this warning?
> 
> seesm like your tex binaries and context scripts are not in sync;

Re: Additional steps taken since the first e-mail

[h h extern]

Mats Broberg wrote:
> Hans,
> 
> OK, and what should I do to remedy this? I am using ConTeXt out of the
> box, as it is when you install MikTeX. 
> 
> Should I download something else from your site? A more recent
> distribution?

if things run fine, you can just ignore the message; normally more methods are 
used to locate files

Hans


-----------------------------------------------------------------
                                           Hans Hagen | PRAGMA ADE
               Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
      tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com
                                              | www.pragma-pod.nl
-----------------------------------------------------------------

Re: Additional steps taken since the first e-mail

[Johannes Werner]

newinstaller,
i struggled more than one day with installation of context. i'm using a 
different OS (redhat linux) and have a different tex-distribution on it 
(tetex), but maybe this hint is useful for you too:
in the tetex-distro there is a file .../texmf/web2c/fmtutil.cnf . in 
this file the lines for context were commented by default - you have to 
uncomment them and run "fmtutil --missing" afterwards (or "fmtutil 
-all", if you have more time). maybe in miktex there's somthing 
similiar. at my first try i forget to run fmtutil, edited texexec.ini 
and run "texexec --make" which worked. but afterwards context had some 
"special features".

Mats Broberg wrote:

>Listmembers,
>
>I have also done the following since the first e-mail:
>
>
>- Copied the contents of "texexec.rme" to "texexec.ini"
>
>- Uncommented the "set TeXShell to miktex" line in the new "texexec.ini"
>file.
>
>- Added the string "C:\texmf\miktex\context\perltk" to the PATH
>(however, there is no "context" or "perltk" folder in the "miktex"
>folder. Shouldn't there be?)
>  
>
no context directory? maybe on a different place (c:\texmf\tex\context ?)

>
>However, the problem still persists.
>
>Best regards,
>Mats Broberg
>
>_______________________________________________
>ntg-context mailing list
>ntg-context@ntg.nl
>http://www.ntg.nl/mailman/listinfo/ntg-context
>
>  
>
mfg, johannes

Re: Additional steps taken since the first e-mail

[VnPenguin]

On Sun, 27 Feb 2005 01:34:00 +0100, Johannes Werner <jowe3659@tiscali.de> wrote:
> newinstaller,
> i struggled more than one day with installation of context. i'm using a
> different OS (redhat linux) and have a different tex-distribution on it
> (tetex), but maybe this hint is useful for you too:
> in the tetex-distro there is a file .../texmf/web2c/fmtutil.cnf . in
> this file the lines for context were commented by default - you have to
> uncomment them and run "fmtutil --missing" afterwards (or "fmtutil
> -all", if you have more time). maybe in miktex there's somthing
> similiar. at my first try i forget to run fmtutil, edited texexec.ini
> and run "texexec --make" which worked. but afterwards context had some
> "special features".

Which version of teTeX ? with "Redhat linux" I imagine that's very
out-of-date tex system, right ?

Re: Additional steps taken since the first e-mail

[Johannes Werner]

VnPenguin wrote:

>On Sun, 27 Feb 2005 01:34:00 +0100, Johannes Werner <jowe3659@tiscali.de> wrote:
>  
>
>>newinstaller,
>>i struggled more than one day with installation of context. i'm using a
>>different OS (redhat linux) and have a different tex-distribution on it
>>(tetex), but maybe this hint is useful for you too:
>>in the tetex-distro there is a file .../texmf/web2c/fmtutil.cnf . in
>>this file the lines for context were commented by default - you have to
>>uncomment them and run "fmtutil --missing" afterwards (or "fmtutil
>>-all", if you have more time). maybe in miktex there's somthing
>>similiar. at my first try i forget to run fmtutil, edited texexec.ini
>>and run "texexec --make" which worked. but afterwards context had some
>>"special features".
>>    
>>
>
>Which version of teTeX ? with "Redhat linux" I imagine that's very
>out-of-date tex system, right ?
>_______________________________________________
>ntg-context mailing list
>ntg-context@ntg.nl
>http://www.ntg.nl/mailman/listinfo/ntg-context
>
>  
>
yepp, what came with redhat 9 is tetex 1.x.x, thatswhy i upgraded to 
2.0.2 . now version 3 is out as an rpm package and i will upgrade again.

RE: Additional steps taken since the first e-mail

[Mats Broberg]

Johannes,

Thanks for the info, but I eventually managed to get the system up and
running last night, and am playing around with it now by testing various
and sundry examples in Hans' manuals. 

I have to say, ConTeXt seems very, very promising for my publication
projects. I lack some features and functions, but all listmembers seem
to be very helpful and hopefully I could eventually get help cooking up
those.

Best regards,
Mats Broberg

On Behalf Of Johannes Werner

> newinstaller,
> i struggled more than one day with installation of context. 
> i'm using a 
> different OS (redhat linux) and have a different 
> tex-distribution on it 
> (tetex), but maybe this hint is useful for you too:
> in the tetex-distro there is a file .../texmf/web2c/fmtutil.cnf . in 
> this file the lines for context were commented by default - 
> you have to 
> uncomment them and run "fmtutil --missing" afterwards (or "fmtutil 
> -all", if you have more time). maybe in miktex there's somthing 
> similiar. at my first try i forget to run fmtutil, edited texexec.ini 
> and run "texexec --make" which worked. but afterwards context 
> had some 
> "special features".

Re: Additional steps taken since the first e-mail

[h h extern]

Johannes Werner wrote:
> newinstaller,
> i struggled more than one day with installation of context. i'm using a 
> different OS (redhat linux) and have a different tex-distribution on it 
> (tetex), but maybe this hint is useful for you too:
> in the tetex-distro there is a file .../texmf/web2c/fmtutil.cnf . in 
> this file the lines for context were commented by default - you have to 
> uncomment them and run "fmtutil --missing" afterwards (or "fmtutil 
> -all", if you have more time). maybe in miktex there's somthing 
> similiar. at my first try i forget to run fmtutil, edited texexec.ini 
> and run "texexec --make" which worked. but afterwards context had some 
> "special features".

texexec --make --alone

will not use fmtutil

(since fmtutil does not support the engine model of tds the latest versions of 
texexec no longer call fmtutil, so if you want to use fmtutil instead you need 
to uncomment those line)

Hans

-----------------------------------------------------------------
                                           Hans Hagen | PRAGMA ADE
               Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
      tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com
                                              | www.pragma-pod.nl
-----------------------------------------------------------------