[Octave-bug-tracker] [bug #53922] unsetenv does not unset environment variables on Windows

[Mike Miller]

Follow-up Comment #4, bug #53922 (project octave):

Octave uses Gnulib for the 'putenv' and 'unsetenv' functions. The 'putenv'
function also allows unsetting an environment variable, but Octave does not
currently use that option. And Gnulib also offers a 'setenv' function that
Octave does not use, maybe it should use that instead of 'putenv'.

I think someone who can test all of the various combinations of these Gnulib
functions in Windows with differently cased environment variables should do
so, and Octave will use whatever the results indicate to use. It's not clear
to me which functions are meant to be used with which other functions.

IMHO, it would be best if Octave supported case sensitive environment
variables even on Windows, just as bash running on Windows appears to.

    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?53922>

_______________________________________________
  Message sent via Savannah
  https://savannah.gnu.org/