From: Mikael Magnusson <mikachu@gmail.com>
To: Bart Schaefer <schaefer@brasslantern.com>
Cc: "Kevin N." <vekinn@gmail.com>, zsh-workers@zsh.org
Subject: Re: Certain unicode in hostname breaks with zsh 4.3.17
Date: Sun, 11 Mar 2012 20:20:02 +0100 [thread overview]
Message-ID: <CAHYJk3TbR4S8NLbH7rut_uf0OBJg_vDzpZFwAqwoDcDBUkab7A@mail.gmail.com> (raw)
In-Reply-To: <CAH+w=7YptzOCFwG3u3g-CvyyenDUFea8rpm7o5g6gzyFzJGx7w@mail.gmail.com>
On 11 March 2012 20:17, Bart Schaefer <schaefer@brasslantern.com> wrote:
> On Sun, Mar 11, 2012 at 12:08 PM, Bart Schaefer
> <schaefer@brasslantern.com> wrote:
>> ** (gnome-terminal:11819): WARNING **: Error (Invalid or incomplete
>> multibyte or wide character) converting data for child, dropping.
>>
>> zsh is probably encountering a similar error.
>
> However, I don't reproduce a crash:
>
> torch% print $ZSH_VERSION
> 4.3.17-dev-0
> torch% HOST="$(perl -MMIME::QuotedPrint -e "print
> decode_qp('=E3=81=95=E3=82=8F=E3=81=93')")"
> ã\M-^A\M-^Uã\M-^B\M-^Oã\M-^A\M-^S%
Regardless of how the data is encoded, shouldn't zsh not be trying to
interpret the value of $HOST as a pattern?
--
Mikael Magnusson
next prev parent reply other threads:[~2012-03-11 19:20 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 [this message]
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
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=CAHYJk3TbR4S8NLbH7rut_uf0OBJg_vDzpZFwAqwoDcDBUkab7A@mail.gmail.com \
--to=mikachu@gmail.com \
--cc=schaefer@brasslantern.com \
--cc=vekinn@gmail.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).