octave-bug-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Octave-bug-tracker] [bug #53922] setenv/unsetenv are case sensitive on


From: Markus Mützel
Subject: [Octave-bug-tracker] [bug #53922] setenv/unsetenv are case sensitive on Windows while getenv is case insensitive
Date: Fri, 28 Sep 2018 19:56:52 -0400 (EDT)
User-agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:63.0) Gecko/20100101 Firefox/63.0

Update of bug #53922 (project octave):

                  Status:               Confirmed => Patch Submitted        
                 Release:                   4.4.0 => dev                    

    _______________________________________________________

Follow-up Comment #15:

The "*env" functions also lack support for non-ASCII characters on Windows.
Among other things, this leads to problems for users with non-ASCII user
name.
Gnulib doesn't support the Windows Unicode API either. So we have to write our
own wrappers anyway if we want to enable users with non-ASCII scripts to use
Octave natively.

The attached patch switches to use the Windows Unicode API for setting,
querying and un-setting environment variables. All of these are
case-insensitive.

There was a bunch of FIXME notes that I just carried over. I don't know
whether they all still apply. Particularly this one in lo-sysdep.cc (after the
patch):

FIXME: make this do the right thing if we don't have a SMART_PUTENV.


Was this referring to the problems with Windows (only)?

See also this short exchange with Mike on the mailing list:
http://octave.1599824.n4.nabble.com/Code-organisation-td4689473.html

(file #45114)
    _______________________________________________________

Additional Item Attachment:

File name: bug53922_getenv_unicode.patch  Size:6 KB


    _______________________________________________________

Reply to this item at:

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

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




reply via email to

[Prev in Thread] Current Thread [Next in Thread]