GNU bug report logs -
#42570
tex-mode compiles / builds only in /tmp
Previous Next
Reported by: RDS <rds1944 <at> gmail.com>
Date: Tue, 28 Jul 2020 03:29:01 UTC
Severity: normal
Tags: moreinfo, notabug
Done: Lars Ingebrigtsen <larsi <at> gnus.org>
Bug is archived. No further changes may be made.
To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 42570 in the body.
You can then email your comments to 42570 AT debbugs.gnu.org in the normal way.
Toggle the display of automated, internal messages from the tracker.
Report forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#42570
; Package
emacs
.
(Tue, 28 Jul 2020 03:29:01 GMT)
Full text and
rfc822 format available.
Acknowledgement sent
to
RDS <rds1944 <at> gmail.com>
:
New bug report received and forwarded. Copy sent to
bug-gnu-emacs <at> gnu.org
.
(Tue, 28 Jul 2020 03:29:01 GMT)
Full text and
rfc822 format available.
Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):
[Message part 1 (text/plain, inline)]
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
[Message part 2 (text/html, inline)]
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#42570
; Package
emacs
.
(Tue, 28 Jul 2020 23:20:02 GMT)
Full text and
rfc822 format available.
Message #8 received at 42570 <at> debbugs.gnu.org (full text, mbox):
[Message part 1 (text/plain, inline)]
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
[Message part 2 (text/html, inline)]
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#42570
; Package
emacs
.
(Tue, 04 Aug 2020 10:27:02 GMT)
Full text and
rfc822 format available.
Message #11 received at 42570 <at> debbugs.gnu.org (full text, mbox):
RDS <rds1944 <at> gmail.com> writes:
> 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.
I'm unable to reproduce this in Emacs 26.3.
Here's my test case:
emacs -nw ~/src/emacs/trunk/etc/refcards/refcard.tex
`C-c C-f' -> a dvi file is made
emacs -nw ~/src/emacs/trunk/etc/refcards/
open refcard.tex
`C-c C-f' -> a dvi file is made
Are you able to reproduce this if you start emacs with -Q?
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
Added tag(s) moreinfo.
Request was from
Lars Ingebrigtsen <larsi <at> gnus.org>
to
control <at> debbugs.gnu.org
.
(Tue, 04 Aug 2020 10:27:02 GMT)
Full text and
rfc822 format available.
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#42570
; Package
emacs
.
(Thu, 06 Aug 2020 02:08:01 GMT)
Full text and
rfc822 format available.
Message #16 received at 42570 <at> debbugs.gnu.org (full text, mbox):
[Message part 1 (text/plain, inline)]
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?
[Message part 2 (text/html, inline)]
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#42570
; Package
emacs
.
(Thu, 06 Aug 2020 07:27:02 GMT)
Full text and
rfc822 format available.
Message #19 received at 42570 <at> debbugs.gnu.org (full text, mbox):
RDS <rds1944 <at> gmail.com> 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
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#42570
; Package
emacs
.
(Fri, 07 Aug 2020 00:35:02 GMT)
Full text and
rfc822 format available.
Message #22 received at 42570 <at> debbugs.gnu.org (full text, mbox):
[Message part 1 (text/plain, inline)]
A test using a Fedora 32 Live image + emacs + texlive-collection-latex
could not replicate the build failure described on this reporter's machine.
The latter has some problem with configuration or missing packages. As
such, these postings should be removed; it is not a bug.
[Message part 2 (text/html, inline)]
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#42570
; Package
emacs
.
(Fri, 07 Aug 2020 07:09:02 GMT)
Full text and
rfc822 format available.
Message #25 received at 42570 <at> debbugs.gnu.org (full text, mbox):
RDS <rds1944 <at> gmail.com> writes:
> A test using a Fedora 32 Live image + emacs + texlive-collection-latex
> could not replicate the build failure described on this reporter's
> machine. The latter has some problem with configuration or missing
> packages. As such, these postings should be removed; it is not a bug.
OK; closing the bug report.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
Added tag(s) notabug.
Request was from
Lars Ingebrigtsen <larsi <at> gnus.org>
to
control <at> debbugs.gnu.org
.
(Fri, 07 Aug 2020 07:09:02 GMT)
Full text and
rfc822 format available.
bug closed, send any further explanations to
42570 <at> debbugs.gnu.org and RDS <rds1944 <at> gmail.com>
Request was from
Lars Ingebrigtsen <larsi <at> gnus.org>
to
control <at> debbugs.gnu.org
.
(Fri, 07 Aug 2020 07:09:02 GMT)
Full text and
rfc822 format available.
bug archived.
Request was from
Debbugs Internal Request <help-debbugs <at> gnu.org>
to
internal_control <at> debbugs.gnu.org
.
(Fri, 04 Sep 2020 11:24:08 GMT)
Full text and
rfc822 format available.
This bug report was last modified 3 years and 235 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.