unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Angelo Graziosi <angelo.g0@libero.it>
Cc: rcopley@gmail.com, emacs-devel@gnu.org
Subject: Re: PATH, exxec-path and early-init file [Windows]
Date: Wed, 12 Aug 2020 16:58:46 +0300	[thread overview]
Message-ID: <83r1scney1.fsf@gnu.org> (raw)
In-Reply-To: <956899396.433746.1597236861815@mail1.libero.it> (message from Angelo Graziosi on Wed, 12 Aug 2020 14:54:21 +0200 (CEST))

> Date: Wed, 12 Aug 2020 14:54:21 +0200 (CEST)
> From: Angelo Graziosi <angelo.g0@libero.it>
> Cc: "emacs-devel@gnu.org" <emacs-devel@gnu.org>
> 
> ..but why early-init.el does not work as one expect?

Why do you think it doesn't?  I've read your original description, and
didn't understand why you thought moving it from the "normal" init
file to early-init would solve the problem.  Perhaps because I don't
understand why you modify PATH from within Emacs, and what does that
have to do with your image DLLs.

> Anyway, it seem that this solves my problem: I create a Windows link (.lnk) whose target is
> 
> C:\msys64\usr\bin\env.exe PATH="/mingw64/bin:$PATH" HOME=/c/Users/utente/AppData/Roaming /c/Emacs/bin/runemacs.exe

The recommended way of doing stuff like that is to change the
system-wide environment, i.e. add the above to your environment
variables, so that you don't need to set this up anew each Emacs
invocation.



      reply	other threads:[~2020-08-12 13:58 UTC|newest]

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

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=83r1scney1.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=angelo.g0@libero.it \
    --cc=emacs-devel@gnu.org \
    --cc=rcopley@gmail.com \
    /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).