unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: rgm@gnu.org, 16429-done@debbugs.gnu.org
Subject: bug#16429: EMACSDATA in the MS Windows registry can interfere with building
Date: Fri, 20 May 2022 17:12:55 +0300	[thread overview]
Message-ID: <83r14o9tso.fsf@gnu.org> (raw)
In-Reply-To: <87h75l6jac.fsf@gnus.org> (message from Lars Ingebrigtsen on Fri,  20 May 2022 04:15:55 +0200)

> From: Lars Ingebrigtsen <larsi@gnus.org>
> Cc: 16429@debbugs.gnu.org, Eli Zaretskii <eliz@gnu.org>
> Date: Fri, 20 May 2022 04:15:55 +0200
> 
> Glenn Morris <rgm@gnu.org> writes:
> 
> > 0cbc41322e clearly adds nothing relevant over e088b01d29.
> > so the comments from https://debbugs.gnu.org/16429#43 presumably still apply.
> 
> This was:
> 
> > Fixed for POSIX platforms.
> > Leaving open with downgraded severity since the MS Windows registry
> > could presumably still be a problem.
> 
> Eli, is there something we should do here on Windows hosts, or is
> defining these variables in the registry just a user error?

I see no reliable way of avoiding the effect of Registry settings on
incompatible Emacs versions.  People who want to be able to run
different Emacs versions on the same machine, including the capability
of building newer versions, should NOT use the Registry for these
settings.  We modified the addpm installation program some time ago to
not create any Registry settings that didn't already exist for this
very reason.

So I've now updated the Emacs manual with the advice not to use the
Registry, and I'm therefore closing this bug.





  reply	other threads:[~2022-05-20 14:12 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-13  7:11 bug#16429: 24.3.50; an issue in mingw making zijianyue
2014-01-13 16:53 ` Eli Zaretskii
2014-01-14  1:12   ` bug#16429: " zijianyue
2014-01-14  5:01     ` Eli Zaretskii
2014-03-18 21:32       ` Juanma Barranquero
2014-03-19  3:49         ` Eli Zaretskii
2014-03-19  4:00           ` Juanma Barranquero
2014-03-19  6:26         ` Glenn Morris
2014-04-11  6:55           ` Glenn Morris
2022-04-21 13:37           ` bug#16429: EMACSDATA in the MS Windows registry can interfere with building Lars Ingebrigtsen
2022-04-21 15:26             ` Glenn Morris
2022-05-20  2:15               ` Lars Ingebrigtsen
2022-05-20 14:12                 ` Eli Zaretskii [this message]
2014-01-13 17:01 ` bug#16429: 24.3.50; an issue in mingw making Glenn Morris
2014-01-13 17:44   ` 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=83r14o9tso.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=16429-done@debbugs.gnu.org \
    --cc=larsi@gnus.org \
    --cc=rgm@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).