From: RDS <rds1944@gmail.com>
To: 42570@debbugs.gnu.org
Subject: bug#42570: Lars suggested tests
Date: Wed, 5 Aug 2020 19:06:23 -0700 [thread overview]
Message-ID: <CABj_U1MUGJjJ-eUWJgoWTid8VPNoiwU1_dX5o04_2kqGAhUhFw@mail.gmail.com> (raw)
In-Reply-To: <CABj_U1Pe5x-Cg+0f+XawpfniKdDsitbegtyNucf5G3yGuzh=4Q@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1152 bytes --]
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?
[-- Attachment #2: Type: text/html, Size: 1326 bytes --]
next prev parent reply other threads:[~2020-08-06 2:06 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-28 2:14 bug#42570: tex-mode compiles / builds only in /tmp RDS
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 ` RDS [this message]
2020-08-06 7:26 ` bug#42570: Lars suggested tests 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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CABj_U1MUGJjJ-eUWJgoWTid8VPNoiwU1_dX5o04_2kqGAhUhFw@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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).