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

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

I am kind of afraid, actually. A simple M-x shell C-x C-c is often enough
to kernel panic Mac OS X, depending on various versions.


On Wed, Aug 13, 2014 at 5:16 PM, Emanuel Berg <embe8573@student.uu.se>
wrote:

> Andrew Pennebaker <andrew.pennebaker@gmail.com> writes:
>
> > 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
>
> Yeah, this is too specific an issue for me to
> contribute.
>
> Did you, in your words, expose the system exec, but not
> as a built-in but just as code? Did you succeed with
> that? If so, do you mind showing us?
>
> What happens if you put a C function in the emacs C
> which does exec, recompile, and then bind that to a
> command? Would that work? Sounds kind of dangerous, but
> you shouldn't be afraid of your computer, of course.
>
> --
> underground experts united
>



-- 
Cheers,

Andrew Pennebaker
www.yellosoft.us