Re: Feature request: Expose system `exec` as a built-in elisp function

[Andrew Pennebaker <andrew.pennebaker@gmail.com>]

Eh, what if you don't want the second emacs call to use the same emacs
configuration, etc. etc. as the parent emacs process?

Feel free to ask the cask project for more details:

https://github.com/cask/cask



On Wed, Aug 13, 2014 at 3:36 PM, Barry Margolin <barmar@alum.mit.edu> wrote:

> In article <mailman.7068.1407955728.1147.help-gnu-emacs@gnu.org>,
>  Andrew Pennebaker <andrew.pennebaker@gmail.com> wrote:
>
> > One example of the worthiness of exec is cask, an Emacs package manager
> > that sometimes wants to fork out to an emacs instance, for editing text
> > files.
>
> I'm not familiar with cask, but usually if you run something within
> Emacs, and it wants you to edit something, you set EDITOR=emacsclient so
> that it goes back to the original Emacs instance. You don't need to
> start a new Emacs instance.
>
> And that still doesn't explain why you would want to kill the original
> Emacs instance when running cask.
>
> --
> Barry Margolin, barmar@alum.mit.edu
> Arlington, MA
> *** PLEASE post questions in newsgroups, not directly to me ***
>



-- 
Cheers,

Andrew Pennebaker
www.yellosoft.us