🚀 go-pugleaf

In article <ANDERSON.92Nov2152534@sapir.cog.jhu.edu>  
anderson@sapir.cog.jhu.edu (Stephen Anderson) writes:
> 
> It's been pointed out to me that the Emacs front end to emacs has the
> path /usr/bin/emacs built in as the place to find an emacs executable.
> This gives you (at least) three choices if you want to use it as a
> front end to the emacs-18.59 executable I posted today: (a) save
> /usr/bin/emacs as /usr/bin/emacs.dist and move /usr/local/bin/emacs
> into /usr/bin; (b) save /usr/bin/emacs as in a, and make a link from
> /usr/local/bin/emacs to /usr/bin/emacs; or (c) Get the Emacs sources,
> and edit the line in EtermView.m that forks the emacs shell to start
> up /usr/local/bin/emacs instead of /usr/bin/emacs. Of these, (a) is in
> some sense the most conservative, since you don't even have to put
> /usr/local/bin on your PATH if you don't have to have anything else
> there (move etags, ctags, and emacsclient in the same way). (b) is
> what I did - so long ago I'd forgotten about it.
> 
> --Steve Anderson

Another alternative is to replace /usr/bin/emacs with a shell script like:

#!/usr/local/bin/tcsh
/usr/local/bin/emacs $1

This has the additional advantage of seeing to that your environment is  
passed to emacs even when it is started from the WorkSpace via Emacs.
--


		Magnus Nordborg
		Department of Biological Sciences
		Stanford University
		magnus@fisher.stanford.edu (NeXT mail preferred)