[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Wrong PATH in MSYS2/MINGW64 builds?

From: Eli Zaretskii
Subject: Re: Wrong PATH in MSYS2/MINGW64 builds?
Date: Thu, 28 May 2015 19:49:56 +0300

> Date: Thu, 28 May 2015 17:41:45 +0200
> From: Angelo Graziosi <address@hidden>
> CC: address@hidden, address@hidden
> The package is a Windows native build. I start it with a link on status 
> bar or Start menu with:
>    Target :  C:\msys64\mingw64\bin\runemacs.exe
>    From   :  C:\msys64\mingw64\bin
> On MSYS2/MINGW64 all executable are installed in C:\msys64\mingw64\bin. 
> The above commands (type bzip2...) where only the short way to say that 
> emacs.exe and bzip2.exe where installed in the same 
> C:\msys64\mingw64\bin directory..
> As I noticed in replaying to Oscar, getenv "PATH" does not show 
> C:\msys64\mingw64\bin in the PATH. For this reason I am asking if this 
> is, in some way, to be expected under Windows or if the MSYS2/MINGW64 
> build should be still tuned..

If bzip2.exe is not on PATH, I don't expect this to work.

>  From your answer, it seems the first. I don't like the idea to change 
> the system-wide PATH.

??? Isn't that what you would do on any other OS?  Also, bzip2 is
useful on its own right, unrelated to Emacs.

> Maybe someone has some idea about how to patch Emacs (on Windows) so
> that at least the directory where is emacs.exe is added to PATH.

I think your problem is with exec-path (which is derived from PATH),
not with PATH directly.

IME, it's a bad idea to have exec-path inside Emacs be different from
PATH outside Emacs, because then you'd have subtle differences between
Emacs looking for programs and programs it invokes (such as the shell,
for example) looking for programs.  So my advice is not to patch Emacs
that way.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]