all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
* Enhanced Carbon TeX-run-LateX
@ 2004-07-06 22:29 Tom Dye
  2004-07-07  2:31 ` Tim McNamara
  2004-07-07 15:38 ` Michael Slass
  0 siblings, 2 replies; 3+ messages in thread
From: Tom Dye @ 2004-07-06 22:29 UTC (permalink / raw)


Aloha emacs masters,

I'm setting up the Enhanced Carbon emacs on several new iMacs, mostly to 
run LaTeX.  When I run the TeX-run-Latex function, tcsh claims it can't 
find latex.  I use the bash shell for all the user accounts, and a "which 
latex" command finds the latex binary just fine.  From the bash prompt I 
launched tcsh, and a "which latex" there found the latex binary, too, 
which leads me to believe that tcsh can see the latex binary (unless it 
was retrieving this info through bash?)

How can I solve this problem?  Do I have to install a .cshrc file to 
direct tcsh to the latex binary?  Or, is there an easy way to have emacs 
send the latex command to the bash shell instead?

Many thanks for your help.

Tom

-- 
Thomas S. Dye 
http://www.tsdye.com

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: Enhanced Carbon TeX-run-LateX
  2004-07-06 22:29 Enhanced Carbon TeX-run-LateX Tom Dye
@ 2004-07-07  2:31 ` Tim McNamara
  2004-07-07 15:38 ` Michael Slass
  1 sibling, 0 replies; 3+ messages in thread
From: Tim McNamara @ 2004-07-07  2:31 UTC (permalink / raw)


Tom Dye <tdye@lava.net> writes:

> Aloha emacs masters,
>
> I'm setting up the Enhanced Carbon emacs on several new iMacs,
> mostly to run LaTeX.  When I run the TeX-run-Latex function, tcsh
> claims it can't find latex.  I use the bash shell for all the user
> accounts, and a "which latex" command finds the latex binary just
> fine.  From the bash prompt I launched tcsh, and a "which latex"
> there found the latex binary, too, which leads me to believe that
> tcsh can see the latex binary (unless it was retrieving this info
> through bash?)
>
> How can I solve this problem?  Do I have to install a .cshrc file to
> direct tcsh to the latex binary?  Or, is there an easy way to have
> emacs send the latex command to the bash shell instead?

Can you modify the command that is sent to be the full/path/to/LaTeX?
That ought to solve the problem, I'd think.  ISTR reading that the
Enhanced Carbon Emacs expects absolute pathnames, and your install of
LaTeX may not be where it is expected.  You ought to be able to
modify the e-LISP function TeX-run-LaTeX, I'd think.

I use Emacs on my aged iMac Rev B, but under X11 rather than using one
of the Carbon based builds due to disk space problems (a 4 GB hard
drive...).  Some of the Carbon builds are pretty slick and do a good
job of appearing OS X-native while retaining normal Emac functionality
and keybindings.  Thanks to Mr. Choi!

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: Enhanced Carbon TeX-run-LateX
  2004-07-06 22:29 Enhanced Carbon TeX-run-LateX Tom Dye
  2004-07-07  2:31 ` Tim McNamara
@ 2004-07-07 15:38 ` Michael Slass
  1 sibling, 0 replies; 3+ messages in thread
From: Michael Slass @ 2004-07-07 15:38 UTC (permalink / raw)


Tom Dye <tdye@lava.net> writes:

>Aloha emacs masters,
>
>I'm setting up the Enhanced Carbon emacs on several new iMacs, mostly to 
>run LaTeX.  When I run the TeX-run-Latex function, tcsh claims it can't 
>find latex.  I use the bash shell for all the user accounts, and a "which 
>latex" command finds the latex binary just fine.  From the bash prompt I 
>launched tcsh, and a "which latex" there found the latex binary, too, 
>which leads me to believe that tcsh can see the latex binary (unless it 
>was retrieving this info through bash?)
>
>How can I solve this problem?  Do I have to install a .cshrc file to 
>direct tcsh to the latex binary?  Or, is there an easy way to have emacs 
>send the latex command to the bash shell instead?
>

A few ideas:

- If you're starting emacs from some kind of desktop shortcut, then
  emacs is inheriting its environment from the desktop, and your
  .*rc files are not necessarily relevant here.  I don't know where
  OS-X gets the desktop environment, but your description of the
  disparity between emacs and bash indicates that their environments
  come from different places.

  If you want to sidestep the issue of where emacs's environment comes
  from, and just fix it, you can see where emacs will look for
  executables for sub-processes by examining the value of exec-path:

  ,----
| exec-path's value is 
|
| ("/usr/kerberos/bin" "/usr/local/bin" "/bin" "/usr/bin"
| "/usr/X11R6/bin" "/home/mikesl/bin" "/usr/java/bin"
| "/home/mikesl/bin" "/usr/java/bin"
| "/usr/libexec/emacs/21.3/i386-redhat-linux")
| 
| 
| Documentation:
| *List of directories to search programs to run in subprocesses.
| Each element is a string (directory name) or nil (try default directory).
| 
| You can customize this variable.
`----

If you don't see the directory where your latex executable resides in
that list, emacs won't find it.  You can add dirs to the list with
(add-to-list 'exec-path "/some/new/path")
or by using the customize interface, if you're more comfortable with that.


- If you're going to make a habit of using emacs to edit LaTeX files,
  I'd recommend using auctex.  It has lots of nifty features, is
  actively maintained, and is well supported.  Google knows where it
  is, and it has installation instructions that come with.  Read those
  before posting "how do I use auctex?" questions. ;)

-- 
Mike Slass

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2004-07-07 15:38 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2004-07-06 22:29 Enhanced Carbon TeX-run-LateX Tom Dye
2004-07-07  2:31 ` Tim McNamara
2004-07-07 15:38 ` Michael Slass

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.