Re: emacs-18.59 pkg for NeXT posted

Thread View: comp.sys.next.misc

3 messages

[T] Back to Threads [V] Tree View [G] Group Articles

3 total messages Started by Charles William Swiger Mon, 02 Nov 1992 14:26

#200

Author: Charles William Swiger
Date: Mon, 02 Nov 1992 14:26

30 lines
2097 bytes

Excerpts from netnews.comp.sys.next.misc: 2-Nov-92 Re: emacs-18.59 pkg
for NeX.. by Stephen Anderson@sapir.c 
> 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.

or (d) Rewrite EtermView.m to look for /usr/local/bin/emacs and then
/usr/bin/emacs; better yet, have it search through current users' search
path for 'emacs'....

Admittedly, (b) is easier.

-Chuck


+---------------------------------------------+ 
|  Charles William Swiger -- CMU sucks rocks  | "The television screen is the
|   AMS & normal mail: cs4w+@andrew.cmu.edu   | retina of the mind's eye."
|    NeXTmail: <temporarily out of order>     |           
+---------------------------------------------+            --Videodrome

Re: emacs-18.59 pkg for NeXT posted

#4301

Author: Michael Gersten
Date: Sun, 13 Dec 1992 02:59

20 lines
1386 bytes

cs4w+@andrew.cmu.edu (Charles William Swiger) writes:
>Excerpts from netnews.comp.sys.next.misc: 2-Nov-92 Re: emacs-18.59 pkg
>for NeX.. by Stephen Anderson@sapir.c 
>> 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
>
>or (d) Rewrite EtermView.m to look for /usr/local/bin/emacs and then
>/usr/bin/emacs; better yet, have it search through current users' search
>path for 'emacs'....

Or, better still, why not use the "system" call and let the shell find it,
or use "execvp/execlp" library calls (the 'p' means search the entire path)?
I'm suprised that more people don't use these.

		Michael
-- 
	Michael Gersten		michael@stb.info.com
NeXT Register Developer (NeRD) # 3860 -- Hire me! Quick!
Will program computers for food (and net connection, health benefits, cash,...)

Re: emacs-18.59 pkg for NeXT posted

#4312

Author: Carl Edman
Date: Sun, 13 Dec 1992 18:05

30 lines
2371 bytes

In article <1992Dec13.025955.13216@stb.info.com> michael@stb.info.com (Michael Gersten) writes:
   cs4w+@andrew.cmu.edu (Charles William Swiger) writes:
   >Excerpts from netnews.comp.sys.next.misc: 2-Nov-92 Re: emacs-18.59 pkg
   >for NeX.. by Stephen Anderson@sapir.c 
   >> 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
   >
   >or (d) Rewrite EtermView.m to look for /usr/local/bin/emacs and then
   >/usr/bin/emacs; better yet, have it search through current users' search
   >path for 'emacs'....

   Or, better still, why not use the "system" call and let the shell find it,
   or use "execvp/execlp" library calls (the 'p' means search the entire path)?
   I'm suprised that more people don't use these.

Why not system(3) ? Because it has a ton of overhead and may do things
you don't want it to do. You should only use it for shell escapes in
you programs and those are fast becoming an anachronism in the age of
job control and security concerns. Why not execvp/execlp(3) ? Because
a user may have several versions of emacs on his system and and the
first one in his default path is not the one he wants to use with
Emacs and setting environment variables is notoriously painful for
Workspace launched applications.

Emacs 3.0 Does The Right Thing and allows you to set the path to the
emacs executable in the preferences. Maybe NeXT should start shipping
it with the OS.

        Carl Edman

Thread Navigation

This is a paginated view of messages in the thread with full content displayed inline.

Messages are displayed in chronological order, with the original post highlighted in green.

Use pagination controls to navigate through all messages in large threads.

Back to All Threads