From: Mikael Magnusson <mikachu@gmail.com>
To: Bart Schaefer <schaefer@brasslantern.com>
Cc: zsh-workers@zsh.org
Subject: Re: Certain unicode in hostname breaks with zsh 4.3.17
Date: Mon, 12 Mar 2012 11:56:50 +0100 [thread overview]
Message-ID: <CAHYJk3TnrkEbgPbb-Py7cMwmodVSZtaYUzGd6oFsya5YJC+3NQ@mail.gmail.com> (raw)
In-Reply-To: <120311205638.ZM21245@torch.brasslantern.com>
On 12 March 2012 04:56, Bart Schaefer <schaefer@brasslantern.com> 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
さわこ%
--
Mikael Magnusson
next prev parent reply other threads:[~2012-03-12 10:56 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-11 5:10 Kevin N.
2012-03-11 16:39 ` Phil Pennock
2012-03-11 19:08 ` Bart Schaefer
2012-03-11 19:17 ` Bart Schaefer
2012-03-11 19:20 ` Mikael Magnusson
2012-03-11 21:19 ` Bart Schaefer
2012-03-11 21:28 ` Mikael Magnusson
2012-03-12 3:56 ` Bart Schaefer
2012-03-12 10:08 ` Peter Stephenson
2012-03-12 11:10 ` Peter Stephenson
2012-03-12 17:07 ` Bart Schaefer
2012-03-12 17:11 ` Peter Stephenson
2012-03-12 10:56 ` Mikael Magnusson [this message]
2012-03-12 10:59 ` Mikael Magnusson
2012-03-12 11:02 ` Mikael Magnusson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAHYJk3TnrkEbgPbb-Py7cMwmodVSZtaYUzGd6oFsya5YJC+3NQ@mail.gmail.com \
--to=mikachu@gmail.com \
--cc=schaefer@brasslantern.com \
--cc=zsh-workers@zsh.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).