unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Arthur Miller <arthur.miller@live.com>
Cc: 48444@debbugs.gnu.org
Subject: bug#48444: 28.0.50; package.el wrong path for package-gnupghome-dir on win10
Date: Sun, 16 May 2021 14:47:17 +0300	[thread overview]
Message-ID: <83a6ouvr22.fsf@gnu.org> (raw)
In-Reply-To: <AM9PR09MB4977136D05C2641D76224E6B962E9@AM9PR09MB4977.eurprd09.prod.outlook.com> (message from Arthur Miller on Sun, 16 May 2021 13:40:18 +0200)

> From: Arthur Miller <arthur.miller@live.com>
> Cc: 48444@debbugs.gnu.org
> Date: Sun, 16 May 2021 13:40:18 +0200
> 
> > If you start Emacs from cmd or from a desktop shortcut, then you can
> > edit the environment variables from Computer->Properties.
> 
> Yeah, I know I can set env vars in system props or via some script
> :), I ment if Emacs can figure it out on it's own. It seems a bit
> annoying if path will vary depending on how I start Emacs and it gives
> different behaviour later on, so setq after start seems to work best for
> me, at least I have total control what Emacs will see after start. 

That's a feature ;-)  You can control the Emacs behavior by changing
the environment variables in the shell from which you start Emacs.

My advice is to set the system properties and never start Emacs from
the MSYS Bash unless you want to try something that really needs the
MSYS executables.





  reply	other threads:[~2021-05-16 11:47 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-15 15:07 bug#48444: 28.0.50; package.el wrong path for package-gnupghome-dir on win10 arthur.miller
2021-05-15 16:04 ` Eli Zaretskii
2021-05-15 19:07   ` Arthur Miller
2021-05-15 19:17     ` Eli Zaretskii
2021-05-16 11:40       ` Arthur Miller
2021-05-16 11:47         ` Eli Zaretskii [this message]
2022-07-13 11:14           ` Lars Ingebrigtsen

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=83a6ouvr22.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=48444@debbugs.gnu.org \
    --cc=arthur.miller@live.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).