unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Angelo Graziosi <angelo.g0@libero.it>
To: "emacs-devel@gnu.org" <emacs-devel@gnu.org>
Subject: PATH, exxec-path and early-init file [Windows]
Date: Wed, 12 Aug 2020 01:05:30 +0200 (CEST)	[thread overview]
Message-ID: <774805960.449268.1597187130831@mail1.libero.it> (raw)

The following regards the build of EMACS MASTER on Windows with MSYS2/MINGW64, whose tree is installed in C:\Emacs.

Trying to not add "C:/msys64/mingw64/bin" at level of Windows PATH, I added this to the init.el file (from https://emacs.stackexchange.com/questions/27326/gui-emacs-sets-the-exec-path-only-from-windows-environment-variable-but-not-from):

(add-to-list 'exec-path "C:/msys64/mingw64/bin")
(setenv "PATH" (mapconcat #'identity exec-path path-separator))

This almost works in the sense that I lose a few graphics elements (the tool bar icons are grayed, those of speed bar are completely lost etc.). So I moved those line to an early-init.el file. Indeed the Emacs manual says:

"...early-init.el. This file is loaded before the package system and GUI is initialized..."

"We do not recommend that you move into early-init.el customizations that can be left in the normal init files. That is because the early init file is read before the GUI is initialized..."

But the result is the same. 

In short without a correct Windows PATH it does not find all the libraries it needs.

It seems that what stated by the manual is a bit confusing: if early-init.el is loaded before GUI initialization, why shouldn't it work?

In any case is there a way to avoid to modify Windows PATH?



             reply	other threads:[~2020-08-11 23:05 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-11 23:05 Angelo Graziosi [this message]
2020-08-12 12:45 ` PATH, exxec-path and early-init file [Windows] Richard Copley
2020-08-12 12:54   ` Angelo Graziosi
2020-08-12 13:58     ` Eli Zaretskii

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=774805960.449268.1597187130831@mail1.libero.it \
    --to=angelo.g0@libero.it \
    --cc=emacs-devel@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).