Re: Unicode allowables in Environment variables

[William DeShazer <earl.deshazer@xxxxxxxxx>]

One interesting observation by the way is that it is on ZDOTDIR that is getting munged.

ZSH_CUSTOM
ZSH
XDG_CONFIG_HOME
XDG_DATA_HOME
XDG_CACHE_HOME

FPATH/fpath
PATH/path

all retain the Crystal Ball Unicode character cleanly through initialization. It is just ZDOTDIR that exhibits the behavior. We will know more soon enough, but I look forward to knowing why someone is picking on ZDOTDIR. It is one of my favorite environment variables, so I take it personally. 😊

With regard to your Valgrind observation, I am not surprised. Few people would hazard to put Unicode characters in their path name, especially non-Portable ones. This may not be tested for. I don’t know Valgrind very well, so I probably shouldn’t speculate too much.

I am surprised it hasn’t shown up in one of the other languages, but maybe the unicode characters for languages were constructed to purposefully keep away from these code-points. These seem to be reserved for all of the coolest characters, if I do say so myself. 

Will

> On Nov 4, 2024, at 15:27, Bart Schaefer <schaefer@xxxxxxxxxxxxxxxx> wrote:
> 
> On Mon, Nov 4, 2024 at 1:11 PM Mark J. Reed <markjreed@xxxxxxxxx> wrote:
>> 
>> I'm not sure why unmetafy() is munging it at all ... Possibly because it proceeds right on past the nul terminator if the string has no Meta in it.
> 
> valgrind reports no OOB errors, FWIW.