From: RDS <rds1944@gmail.com>
To: 42570@debbugs.gnu.org
Subject: bug#42570: tex-mode compiles / builds only in /tmp
Date: Mon, 27 Jul 2020 19:14:47 -0700 [thread overview]
Message-ID: <CABj_U1Pe5x-Cg+0f+XawpfniKdDsitbegtyNucf5G3yGuzh=4Q@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 787 bytes --]
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
[-- Attachment #2: Type: text/html, Size: 979 bytes --]
next reply other threads:[~2020-07-28 2:14 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-28 2:14 RDS [this message]
2020-07-28 23:19 ` bug#42570: tex-mode compiles / builds only in /tmp - more info RDS
2020-08-04 10:25 ` Lars Ingebrigtsen
2020-08-06 2:06 ` bug#42570: Lars suggested tests RDS
2020-08-06 7:26 ` Lars Ingebrigtsen
-- strict thread matches above, loose matches on Subject: below --
2020-07-31 0:25 bug#42624: emacs 26.3 : tex-mode.el : tex & latex compile failures RDS
2020-08-02 2:27 ` RDS
2020-08-03 18:09 ` bug#42624: Additional solutions RDS
2020-08-03 20:35 ` bug#42624: More info RDS
2020-08-07 0:33 ` bug#42624: emacs - tex-mode.el - build failure - not a bug RDS
2020-08-07 7:08 ` bug#42570: " Lars Ingebrigtsen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CABj_U1Pe5x-Cg+0f+XawpfniKdDsitbegtyNucf5G3yGuzh=4Q@mail.gmail.com' \
--to=rds1944@gmail.com \
--cc=42570@debbugs.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.