no executable emacs binary in exec-directory

no executable emacs binary in exec-directory

[Lennart Borgman]

I thought that the currently running emacs binary should be in
exec-directory. That does not seem to be the case always. How do you
find it?

Re: no executable emacs binary in exec-directory

[Sven Joachim]

On 2008-11-29 14:00 +0100, Lennart Borgman wrote:

> I thought that the currently running emacs binary should be in
> exec-directory. That does not seem to be the case always.

Actually, on GNU/Linux this should never be the case.

> How do you find it?

It is in invocation-directory, and its name is invocation-name.

Sven

Re: no executable emacs binary in exec-directory

[Juanma Barranquero]

On Sat, Nov 29, 2008 at 14:23, Sven Joachim <svenjoac@gmx.de> wrote:

> Actually, on GNU/Linux this should never be the case.

Not even when you build in place?

  Juanma

Re: no executable emacs binary in exec-directory

[Stephen J. Turnbull]

Juanma Barranquero writes:
 > On Sat, Nov 29, 2008 at 14:23, Sven Joachim <svenjoac@gmx.de> wrote:

 > > Actually, on GNU/Linux [emacs found in exec-directory should
 > > never be the case.
 > 
 > Not even when you build in place?

exec-directory is where emacs finds its bundled copies of utilities
like movemail and etags.  When running-in-place, that's lib-src.  So,
no.  The emacs binary should be on $PATH, not in exec-directory.

Re: no executable emacs binary in exec-directory

[Lennart Borgman]

On Sat, Nov 29, 2008 at 2:46 PM, Stephen J. Turnbull
<turnbull@sk.tsukuba.ac.jp> wrote:
> Juanma Barranquero writes:
>  > On Sat, Nov 29, 2008 at 14:23, Sven Joachim <svenjoac@gmx.de> wrote:
>
>  > > Actually, on GNU/Linux [emacs found in exec-directory should
>  > > never be the case.
>  >
>  > Not even when you build in place?
>
> exec-directory is where emacs finds its bundled copies of utilities
> like movemail and etags.  When running-in-place, that's lib-src.  So,
> no.  The emacs binary should be on $PATH, not in exec-directory.

I do not think that the emacs binary always should be on PATH. On w32
that is not usually the way to handle it.

Re: no executable emacs binary in exec-directory

[Sven Joachim]

On 2008-11-29 14:26 +0100, Juanma Barranquero wrote:

> On Sat, Nov 29, 2008 at 14:23, Sven Joachim <svenjoac@gmx.de> wrote:
>
>> Actually, on GNU/Linux this should never be the case.
>
> Not even when you build in place?

Not even then, in this case emacs is built in src, while the helper
binaries live in lib-src.

Well, actually there is one possibility where invocation-directory is
the same as exec-directory: if you pass the same values for --bindir and
--libexecdir to `configure'.

Sven

Re: no executable emacs binary in exec-directory

[Juanma Barranquero]

On Sat, Nov 29, 2008 at 14:46, Sven Joachim <svenjoac@gmx.de> wrote:

> Well, actually there is one possibility where invocation-directory is
> the same as exec-directory: if you pass the same values for --bindir and
> --libexecdir to `configure'.

Aha. In Windows, these are both conflated into bin/.

Thanks (and Stephen, too).

  Juanma

Re: no executable emacs binary in exec-directory

[Lennart Borgman]

On Sat, Nov 29, 2008 at 2:23 PM, Sven Joachim <svenjoac@gmx.de> wrote:
> On 2008-11-29 14:00 +0100, Lennart Borgman wrote:
>
>> I thought that the currently running emacs binary should be in
>> exec-directory. That does not seem to be the case always.
>
> Actually, on GNU/Linux this should never be the case.
>
>> How do you find it?
>
> It is in invocation-directory, and its name is invocation-name.

Thanks. Is this then the way to find the executable?

(defun ourcomments-find-emacs-executable ()
  (let ((exec-path (list invocation-directory)))
    (executable-find invocation-name)))

Re: no executable emacs binary in exec-directory

[Lennart Borgman]

On Sat, Nov 29, 2008 at 2:41 PM, Lennart Borgman
<lennart.borgman@gmail.com> wrote:
> On Sat, Nov 29, 2008 at 2:23 PM, Sven Joachim <svenjoac@gmx.de> wrote:
>> On 2008-11-29 14:00 +0100, Lennart Borgman wrote:
>>
>>> I thought that the currently running emacs binary should be in
>>> exec-directory. That does not seem to be the case always.
>>
>> Actually, on GNU/Linux this should never be the case.
>>
>>> How do you find it?
>>
>> It is in invocation-directory, and its name is invocation-name.
>
> Thanks. Is this then the way to find the executable?
>
> (defun ourcomments-find-emacs-executable ()
>  (let ((exec-path (list invocation-directory)))
>    (executable-find invocation-name)))

Hm, this looks better, but I wonder about the "1".

(defun ourcomments-find-emacs ()
  (locate-file invocation-name
               (list invocation-directory)
               exec-suffixes
               1 ;; Depreceated, but used in executable-find
               ))

Re: no executable emacs binary in exec-directory

[Stefan Monnier]

>> (defun ourcomments-find-emacs-executable ()
>> (let ((exec-path (list invocation-directory)))
>> (executable-find invocation-name)))

> Hm, this looks better, but I wonder about the "1".

> (defun ourcomments-find-emacs ()
>   (locate-file invocation-name
>                (list invocation-directory)
>                exec-suffixes
>                1 ;; Depreceated, but used in executable-find
>                ))

Why does it look better to you?


        Stefan

Re: no executable emacs binary in exec-directory

[Lennart Borgman]

On Sat, Nov 29, 2008 at 8:59 PM, Stefan Monnier
<monnier@iro.umontreal.ca> wrote:
>>> (defun ourcomments-find-emacs-executable ()
>>> (let ((exec-path (list invocation-directory)))
>>> (executable-find invocation-name)))
>
>> Hm, this looks better, but I wonder about the "1".
>
>> (defun ourcomments-find-emacs ()
>>   (locate-file invocation-name
>>                (list invocation-directory)
>>                exec-suffixes
>>                1 ;; Depreceated, but used in executable-find
>>                ))
>
> Why does it look better to you?

I feel that it more explicitly mentions in which directory the search
is made. But I might change my mind about that tomorrow ... ;-)