Zsh Mailing List Archive
Messages sorted by: Reverse Date, Date, Thread, Author

Re: Certain unicode in hostname breaks with zsh 4.3.17



On 12 March 2012 11:59, Mikael Magnusson <mikachu@xxxxxxxxx> wrote:
> On 12 March 2012 11:56, Mikael Magnusson <mikachu@xxxxxxxxx> wrote:
>> On 12 March 2012 04:56, Bart Schaefer <schaefer@xxxxxxxxxxxxxxxx> wrote:
>>> On Mar 11, 10:28pm, Mikael Magnusson wrote:
>>> }
>>> } 0x308C0x306B0x306A% echo $HOST
>>> } zsh: no matches found: \M-c\M-^B|0x306B0x306A
>>>
>>> Hm.
>>>
>>>    hostnam = (char *)zalloc(256);
>>>    gethostname(hostnam, 256);
>>>    setsparam("HOST", ztrdup(hostnam));
>>>    zfree(hostnam, 256);
>>>
>>> Apparently that ztrdup(hostnam) should be a metafy(hostnam, -1, META_DUP).
>>>
>>> Should that get done with LOGNAME, MACHTYPE, OSTYPE, and VENDOR as well?
>>>
>>> None of that explains the OP's crash, though.  The above code excerpt has
>>> not changed in at least a dozen years, and he says 4.3.15 did not show a
>>> problem.
>>
>> I asked him on irc, and his crash comes from compdump, i think this line,
>> mv -f $_d_file ${_d_file%.$HOST.$$}
>> It doesn't crash for me though,
>> % zsh -f
>> さわこ% autoload compinit
>> さわこ% compinit
>> compdump:135: bad pattern: .\M-c\M-^A?\M-c\M-^B[\M-c\M-^A>.11450
>> さわこ%
>
> Apparently he can't reproduce the crash anymore, only the bad pattern message.

Sorry for triple posting, apparently there was some confusion with
compdump vs coredump, there was never a crash :).

-- 
Mikael Magnusson



Messages sorted by: Reverse Date, Date, Thread, Author