all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Juanma Barranquero <jmbarranquero@wke.es>
Subject: Re: (Windows:) cmdproxy non-existent on bootstrapping after make	realclean
Date: Mon, 22 Mar 2004 12:38:19 +0100	[thread overview]
Message-ID: <20040322111734.ACD6.JMBARRANQUERO@wke.es> (raw)
In-Reply-To: <uoeqpig7x.fsf@elta.co.il>


On 22 Mar 2004 07:49:22 +0200
Eli Zaretskii <eliz@elta.co.il> wrote:

> Is it true that the variables in the registry are actually pushed
> into the environment of the running Emacs, so that `getenv' sees
> them?

Well, if I change HKLM\SOFTWARE\GNU\Emacs\SHELL to point to a
non-existent exe, M-x shell fails, so yes.

> I don't think this is a hack no more than the whole Makefile system
> for building Emacs on Windows, which is already full of worse tricks
> in order to support the different makes of shells, compilers, and Make
> varieties.

The "hack", in my view, is having to process %COMSPEC% to escape \'s
before passing it to Emacs. But, hey, I agree: the Windows makefile
system is a bit of a nightmare (though I *fully* understand why it's
done the way it is, I'm not pointing fingers).

> If so, can we override these variables with real environment
> variables set either by the shell or by Make?

Yes, you're right! I overlooked that :)

So, you're proposing this fix instead of deleting the registry entries?
If so, what's a good default to SHELL? %COMSPEC%?


                                                                Juanma

  reply	other threads:[~2004-03-22 11:38 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-21 18:01 (Windows:) cmdproxy non-existent on bootstrapping after make realclean Juanma Barranquero
2004-03-22  5:49 ` Eli Zaretskii
2004-03-22 11:38   ` Juanma Barranquero [this message]
2004-03-22 19:00     ` 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

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

  git send-email \
    --in-reply-to=20040322111734.ACD6.JMBARRANQUERO@wke.es \
    --to=jmbarranquero@wke.es \
    /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 external index

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

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.