bug#42570: tex-mode compiles / builds only in /tmp

classic Classic list List threaded Threaded
4 messages Options
Reply | Threaded
Open this post in threaded view
|

bug#42570: tex-mode compiles / builds only in /tmp

_RDS_
emacs 26.3. 2 different builds. 2 distinct OSs.

One build is custom inside Slackware; another build is standard issue from Fedora 32.

Results below are identical for both situations.

If the tex / latex source (or a symbolic link) resides in /tmp directory, everything from the tex mode menu functions as expected.

If the source is anywhere else in the directory structure, the first step, compilation (tex / latex), fails because it can *not* find the source file. Yet, if I use my own custom elisp script or invoke the relevant commands manually, there is *no* problem.

The builtin tex-mode.el script seems to expect all code to be only in /tmp or nothing will occur.

Am I missing something? A variable setting? Some other configuration aspect?

Thanks for your attention.

Guido

Reply | Threaded
Open this post in threaded view
|

bug#42570: tex-mode compiles / builds only in /tmp - more info

_RDS_
Invoking
    emacs  /path/to/file.tex
followed by C-c C-f does work.

But doing
    emacs  /path/to
then opening file.tex from dired followed by C-c C-f does not work.

Apparently tex-mode.el is not sending the correct full path to pdftex; it does not find the input file under many circumstances.

Guido

Reply | Threaded
Open this post in threaded view
|

bug#42570: Lars suggested tests

_RDS_
In reply to this post by _RDS_
I have tried the tests you suggest on refcard.tex (plus a few others in that dir) with & without -Q cl switch; nearly all failed to produce a dvi. Immediately tex fails since it can *not* find the source file as I described previously. (Also review additional material in bug 42624.) The results are identical on both a Slackware-current partition installation & on a Fedora 32 partition installation.

The Texlive installations are current & direct compilation on any tex / latex source files functions flawlessly. I also have a tiny piece of lisp code that directly invokes, via start-process, the tex / latex compiler; it, too, never has a problem.

Reiterating, the tex-shell created by tex-mode.el does *not* see a path to the source unless modifications I suggest are made as in bug 42624.

Is this possibly a configuration issue? Could there be hidden environmental variables that need to be set either in my bash shell or something I am missing in the init.el? Official emacs documentation about tex-mode says little about this matter. As an aside, inside tex-mode.el, there is a getenv ESHELL command. Does ESHELL need some special attention?

Reply | Threaded
Open this post in threaded view
|

bug#42570: Lars suggested tests

Lars Ingebrigtsen
RDS <[hidden email]> writes:

> Is this possibly a configuration issue? Could there be hidden
> environmental variables that need to be set either in my bash shell or
> something I am missing in the init.el?

I don't know -- I've tried your recipe for the bug on two different
(Debian and Ubuntu) machines, and I'm unable to reproduce it with "emacs
-Q" on Emacs 26.3.

So I think it sounds like a configuration issue on your side somewhere,
but I haven't used tex otherwise in quite a few years.

--
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no