|
From: | npostavs |
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 |
User-agent: | Gnus/5.13 (Gnus v5.13) Emacs/25.1 (gnu/linux) |
Ó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.
[Prev in Thread] | Current Thread | [Next in Thread] |