I figured it out! I feel really stupid... But I figured it out.<div><br></div><div>I had to add <br><br></div><div>(setq exec-path (append exec-path '("path/to/gs")))</div><div><br></div><div>to my .emacs file. I'm not sure why this worked and why my previous .emacs setup didn't... I'm assuming it's the difference between the exec-path and the PATH? Thanks for all your help everyone! I should make a web page about this in case I need to do it again...<br>
<br><div class="gmail_quote">On Fri, Mar 12, 2010 at 9:13 PM, John Mark Swafford <span dir="ltr"><<a href="mailto:johnmarksuave@gmail.com">johnmarksuave@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<br><br><div class="gmail_quote"><div><div></div><div class="h5">On Fri, Mar 12, 2010 at 7:26 PM, Peter Dyballa <span dir="ltr"><<a href="mailto:Peter_Dyballa@web.de" target="_blank">Peter_Dyballa@web.de</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
Am 12.03.2010 um 00:37 schrieb John Mark Swafford:<div><br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
./configure --with-gif=no --with-ns<br>
make<br>
make install<br>
sudo cp -r nextstep/Emacs.app /Applications/Emacs.app<br>
</blockquote>
<br></div>
The last step has possibly three faults:<br>
<br>
1) the sudo<br>
2) the 'cp -r'<br>
3) the '/Applications/Emacs.app' target<br>
<br>
Final step 1 is *not* needed. When you're allowed to sudo then you're automatically, I think, member of the group admin and therefore have write privileges in /Applications. I am member and I can easily drag things into /Applications or remove other things from there.<br>
<br>
Final step 2 looks like a command which might work correctly. I have my doubts, based on heuristics gained somewhen in the last, maybe, ten years. I'd drag Emacs.app to /Applications:<br>
<br>
open nextstep<br>
open /Applications<br>
« delete old Emacs.app in Applications »<br>
« drag Emacs.app from nextstep to Applications »<br>
<br>
Final step 3 is definitely wrong! You can overwrite the old software, however this is the source for a cascade of faults. It's not guaranteed that old files are removed. It's not guaranteed that a file with the same name is moved into another sub-directory as it has happened in the new source, with the effect that now two files of different revision exist in Emacs' load-path.<br>
<br>
When you install the new version of an application then this "application bundle" has means to first move the old version into the trash can. Then it "installs" itself in /Applications. You have to mimic this on the command line, i.e., after 'make install' a '(sudo) rm -rf /Applications/Emacs.app' has to happen. Or just drag...<div>
<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
When I have a .tex document open, it says [(LaTeX ht Fill)] in the mode-line.<br>
</blockquote>
<br>
<br></div>
The 'ht' snippet is definitely incorrect. Then the whole Emacs.app cannot be right.<br><font color="#888888">
<br></font></blockquote><div><br></div></div></div><div>Ok, I reinstalled Emacs according to Peter. Now the mode line in my main.tex file simply says (LaTeX). </div><div><br></div>I also installed AUCTeX. I used the following to configure it (via Axel's suggestion):<div>
<br></div><div>./configure --with-emacs=/Applications/Emacs.app/Contents/MacOS/Emacs --with-lispdir=/Applications/Emacs.app/Contents/Resources/site-lisp --without-texmf-dir</div><div>make</div><div>sudo make install</div>
<div><br></div><div>Like before, I got rid of my customized .emacs file just in case anything in it was causing an unexpected problem. My new .emacs looks like this:</div><div><br></div><div><div>(setenv "PATH"</div>
<div> (concat</div><div> "/usr/local/bin" ":"</div><div> "/usr/local/sbin" ":"</div><div> "/usr/local" ":"</div><div> "/bin" ":"</div>
<div> "/opt/local/bin" ":"</div><div> "/opt/local/sbin" ":"</div><div> "/usr/X11/bin" ":"</div><div> "/usr/X11R6/bin"</div><div> ))</div>
<div><br></div><div>(require 'tex-site)</div><div><br></div><div>;; Don't load the startup screen. It's obnoxious</div><div>(setq inhibit-startup-message t)</div><div>(setq inhibit-splash-screen t)</div><div>
<br>
</div><div>(load "auctex.el" nil t t)</div><div>(load "preview-latex.el" nil t t)</div><div><br></div><div>Without the setenv at the top, my Emacs can't find ANYTHING, not latex, not dvips, not anything. I added the last parts to make sure Emacs was finding AUCTeX and could load it properly. Next, I opened my main.tex file and compiled it with LaTeX. This worked fine. When I pressed C-c C-c, Emacs tried to open my file in xdvi. I can change this later, so I'm not worried about that. However, when I try and use M-x preview-document (this comes with the preview-latex.el packaged with AUCTeX, I think) I get this:</div>
<div><br></div><div>error in process sentinel: Searching for program: No such file or directory, gs</div><div><br></div></div><div>This is probably my problem as to why DocView isn't working, but it doesn't make much sense to me because gs is in the same directory as everything else! Is there a way to set the path to gs somewhere else that I'm missing?</div>
<div><br></div><div>Also, I tried simply opening a .dvi and a .pdf file just to see what errors I was given. When opening a .dvi I get the following:</div><div><br></div><div>No PNG support is available, or some conversion utility for dvi files is missing.</div>
<div>File mode specification error: (wrong-type-argument stringp nil)</div><div><br></div><div>When opening a .pdf I get:</div><div><br></div><div>No PNG support is available, or some conversion utility for pdf files is missing.</div>
<div>File mode specification error: (wrong-type-argument stringp nil) </div><div><br></div><div>This also makes me think Emacs isn't finding my gs, but when I run:</div><div><br></div><div>which gs</div><div><br></div>
<div>in an Emacs shell, it shows me the correct path. Has anyone else has issues like this setting up their Emacs on OS X to work with DocView properly?</div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<font color="#888888">
<br>
</font><br>_____________________________________________________________<br>
MacOSX-Emacs mailing list<br>
<a href="mailto:MacOSX-Emacs@email.esm.psu.edu" target="_blank">MacOSX-Emacs@email.esm.psu.edu</a><br>
<a href="http://email.esm.psu.edu/mailman/listinfo/macosx-emacs" target="_blank">http://email.esm.psu.edu/mailman/listinfo/macosx-emacs</a><br>
List Archives: <a href="http://dir.gmane.org/gmane.emacs.macintosh.osx" target="_blank">http://dir.gmane.org/gmane.emacs.macintosh.osx</a><br>
<br></blockquote></div><br>
</blockquote></div><br></div>