----- Original Message -----
From: "Pablo Ortúzar" <[EMAIL PROTECTED]>
To: <[email protected]>
Sent: Monday, August 29, 2005 12:48 AM
Subject: Re: No classes
On Monday 29 August 2005 00:39, Stephen P. Harris wrote:
----- Original Message -----
From: "Paul A. Rubin" <[EMAIL PROTECTED]>
> Pablo Ortúzar wrote:
> The article.cls file should be in the ./tex/latex/base folder under your
> LaTeX installation. Is it there? If not, the teTeX installation may be
> hosed. If it is there, then I suspect there's a problem with
> environment
>
> variables. Quoting the teTeX FAQ:
>> The file texmf.cnf is searched for in $SELFAUTODIR, $SELFAUTOPARENT,
>> $TETEXDIR. If the file texmf.cnf is not found, set the TETEXDIR
>> variable
>> in your environment.
>
> Are those variables set in your environment?
>
> Paul
I think there is a possibility that if article.cls exists and is not
found,
that some old file like .bash_profile or /etc/profile or even .login might
have a prior defining entry which points to older locations of files and
which could possibly differ from a newer version of teTeX, or maybe
even Suse 10 beta, which could change the previous default installation
of files and create a gun loaded with blanks pointing at the wrong
culprit.
Still, it seems most likely that many .cls are genuinely missing in action
rather than being held incognito as political hostages.
---------------------------------------------------------------------------
---- http://people.freebsd.org/~hrs/tetex-upgrade.txt
"(5 Jun 2005) Note that if you have environment variables for teTeX
in a wrong way (such as TEXINPUTS, TEXMF, TEXMFCNF, and so
on), they may prevent teTeX from working. Please unset them first if
you do not know what they are for since typically they are not needed.
However, some TeX related packages may suggest to set TEXINPUTS.
In that case, please make sure the TEXINPUTS includes a trailing ":"
character, which indicates the standard search paths are also used."
---------------------------------------------------------------------------
----
Tags,
Stephen
Thanks. I went back to Mandrake LE2005, and Lyx is -again- working as usual.
All classes *can't* be missing in the SuSE LaTeX rpm, so I tend to believe
that -perhaps because the search paths are wrong- Lyx couldn't find them.
--
Pablo Ortúzar
SH: Does that mean the same as, because the directory structure is
wrong and the files have not been installed in the correct directories
that this is entire source of the problem?
The question is not if all classes are missing from the Suse LaTex rpm,
or if any are missing.
The question is if all classes were installed and physically exist on
your computer. "kpsewhich article.cls" only discovers if article.cls
is installed in the correct location: .../texmf/tex/latex/base
That is the directory structure for both Windows and Linux and
besides article.cls there are other .cls files installed there.
Using "kpsewhich article.cls" which produced "nothing" proved that
the *tex installation was faulty just as Paul explained. Whether or not
*.cls was installed somewhere on your computer or not at all was a
simple fact to determine. That is why I suggested that from root, type
"find / -name article.cls"
That would have told you if article.cls actually existed on your
computer and if it did, then you could have inferred that the rest
of the .../base .cls files also physically existed. But they would be
in the wrong directory. The problem was that article.cls and probably
other .cls were not in the correct directory (or did not exist at all).
I think that on Mandriva if you type kpsewhich article.cls is will
report .../texmf/tex/latex/base
And if you copy article.cls into some /docs directory and rename
article.cls to article.bak, then I don't think LyX will work properly
and that is not the fault of LyX. But whoever or whatever improperly
installed *tex in the first place, that changed the default directory
structure so that article.cls and others are misplaced like the example
above of putting article.cls in a /docs directory (or not installed at all).
