From: Garglemonster <garglemonster@my-deja.com>
Subject: Re: auctex + texlive = problems
Date: Wed, 26 Mar 2003 12:11:37 +0900 [thread overview]
Message-ID: <87el4ult3q.fsf@shroud.disorg> (raw)
In-Reply-To: 84d6kgihd9.fsf@lucy.is.informatik.uni-duisburg.de
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=iso-2022-jp-2, Size: 1231 bytes --]
>>>>> "Kai" == Kai Gro^[.A^[N_johann <kai.grossjohann@uni-duisburg.de> writes:
Kai> Garglemonster <garglemonster@my-deja.com> writes:
>> i recently switched my laptop over to texlive from tetex. now
>> i find that i can't get auctex to compile latex files unless i
>> start emacs from a terminal window command prompt. (it tells
>> me it can't find the latex binary) i've used customise to set
>> up the latex commands to reflect the locations of the new
>> binaries. i have TEXINPUTS, TEXMF and TEX_PATH set in my
>> .bashrc. what am i forgetting?
Kai> Maybe $PATH?
i have stuff set up like this in my .bashrc :
FOO_PATH=/blah/blah:/usr/blah/blah
BAR_PATH=/yadda/yadda:/usr/yadda/yadda:/usr/local/yadda/yadda
PATH=$FOO_PATH:$BAR_PATH
checked again, and i haven't forgotten to add any of the relevant
$TEX_STUFF. however, just in case anyone was worried, i don't think
this is an emacs/auctex problem since i've discovered that i can no
longer compile latex files in console. (this is on slackware linux 9)
things do work on an rxvt console in x, though. problem must be
elsewhere. thanks for your help, though.
--
garglemonster@my-deja.com
There are alternatives to war AND oil
next prev parent reply other threads:[~2003-03-26 3:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-17 17:12 auctex + texlive = problems Garglemonster
2003-03-18 13:05 ` Pierre Albarede
2003-03-24 21:28 ` Kai Großjohann
2003-03-26 3:11 ` Garglemonster [this message]
2003-03-26 8:06 ` David Kastrup
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=87el4ult3q.fsf@shroud.disorg \
--to=garglemonster@my-deja.com \
/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.