all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: npostavs@users.sourceforge.net
To: "Óscar Fuentes" <ofv@wanadoo.es>
Cc: 24956@debbugs.gnu.org
Subject: bug#24956: 26.0.50; On Windows, setting PATH in compilation-environment has no effect
Date: Sun, 27 Nov 2016 15:13:06 -0500	[thread overview]
Message-ID: <87h96sisvh.fsf@users.sourceforge.net> (raw)
In-Reply-To: <87mvgk4rq4.fsf@wanadoo.es> ("Óscar Fuentes"'s message of "Sun, 27 Nov 2016 21:01:39 +0100")

Óscar Fuentes <ofv@wanadoo.es> writes:

> Eli Zaretskii <eliz@gnu.org> writes:
>
>>> Oops. Looking at Fupcase, I had somehow thought that unibyte vs
>>> multibyte would be a problem (and hence I should use Fcompare_strings
>>> to hide the details), but actually (as I think you've mentioned
>>> before) that's not the case for environment variables.
>>> 
>>> Here's a new patch.
>>
>> Looks OK to me, thanks.
>
> Ping.
>
> I'll like to mark this as resolved. Noam?

I'm not in front of my Windows box right now, I'm planning to push this tomorrow.





  reply	other threads:[~2016-11-27 20:13 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-16 22:22 bug#24956: 26.0.50; On Windows, setting PATH in compilation-environment has no effect Óscar Fuentes
2016-11-17 17:59 ` Noam Postavsky
2016-11-17 20:59   ` Eli Zaretskii
2016-11-17 21:27     ` Noam Postavsky
2016-11-18  9:46       ` Eli Zaretskii
2016-11-18 22:11         ` Noam Postavsky
2016-11-19  7:16           ` Eli Zaretskii
2016-11-21 23:19             ` Noam Postavsky
2016-11-22 16:01               ` Eli Zaretskii
2016-11-22 22:35                 ` Noam Postavsky
2016-11-23 16:07                   ` Eli Zaretskii
2016-11-27 20:01                     ` Óscar Fuentes
2016-11-27 20:13                       ` npostavs [this message]
2016-11-28 22:53                         ` Noam Postavsky

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=87h96sisvh.fsf@users.sourceforge.net \
    --to=npostavs@users.sourceforge.net \
    --cc=24956@debbugs.gnu.org \
    --cc=ofv@wanadoo.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.