[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Async package.el
From: |
Robert Pluim |
Subject: |
Re: Async package.el |
Date: |
Tue, 07 Apr 2015 16:29:05 +0200 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/25.0.50 (gnu/linux) |
Artur Malabarba <address@hidden> writes:
>> Using a second Emacs runs the risk that it's not the same version as the
>> running Emacs. How likely is that to happen? For instance, the only Emacs in
>> my path is not the one I'm typing this in.
>
> Your system path is irrelevant in this scenario. Emacs can tell the
> full filename of the executable that's running it with
> `(expand-file-name invocation-name invocation-directory)', and that is
> what we would use to run the second instance.
OK.
> The only situation where they can diverge is if the Emacs executable
> was recompiled while the current one is running, and then we could add
> some form of version check to protect against it.
That happens to me sometimes as well, but in that case I've pointed the
gun at my own foot and pulled the trigger :-) I'd consider it rare
enough that you don't need to expend a lot of effort to prevent it.
- Re: Async package.el, (continued)
- Re: Async package.el, Artur Malabarba, 2015/04/08
- Re: Async package.el, Dmitry Gutov, 2015/04/08
- Re: Async package.el, Artur Malabarba, 2015/04/09
- Re: Async package.el, Dmitry Gutov, 2015/04/09
- Re: Async package.el, Artur Malabarba, 2015/04/11
- Re: Async package.el, Daiki Ueno, 2015/04/07
- Re: Async package.el, Dmitry Gutov, 2015/04/07
- Re: Async package.el, Artur Malabarba, 2015/04/07
- Re: Async package.el, Robert Pluim, 2015/04/07
- Re: Async package.el, Artur Malabarba, 2015/04/07
- Re: Async package.el,
Robert Pluim <=
- Re: Async package.el, Artur Malabarba, 2015/04/07
- Re: Async package.el, Stefan Monnier, 2015/04/07
- Re: Async package.el, Daiki Ueno, 2015/04/08
- Re: Async package.el, Achim Gratz, 2015/04/09
- Re: Async package.el, Stefan Monnier, 2015/04/09
Re: Async package.el, Stefan Monnier, 2015/04/07