From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <zsh-workers-return-33102-mason-zsh=primenet.com.au@zsh.org>
Received: (qmail 10268 invoked by alias); 3 Sep 2014 08:00:54 -0000
Mailing-List: contact zsh-workers-help@zsh.org; run by ezmlm
Precedence: bulk
X-No-Archive: yes
List-Id: Zsh Workers List <zsh-workers.zsh.org>
List-Post: <mailto:zsh-workers@zsh.org>
List-Help: <mailto:zsh-workers-help@zsh.org>
X-Seq: 33102
Received: (qmail 17786 invoked from network); 3 Sep 2014 08:00:52 -0000
X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on f.primenet.com.au
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 required=5.0 tests=BAYES_00,DKIM_SIGNED,
	DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW autolearn=ham
	version=3.3.2
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :cc:content-type:content-transfer-encoding;
        bh=oxEvTkizpYvJueY0OU/Prm1CgWhjuxkojP3Znq62Slo=;
        b=a0ThSkj0lDmChGigfS3UqI8rSRKs/meYGPolwW1ntX1TLx8Yz8bvBEAN0lLx3FGDNN
         UIL81JVX+nzX2Q67aYH/tkZ9e8kjwvGRv5AWLstFNV2Lby4OCQCQucYfhgvKUSctjm59
         9eGK3ZtXAu+Qt9AQCzug1DfTZmDlx7aX18EjvNYu6XfaQNq52xe4hiLCF2NlR6mTPFXc
         zG3L0m54lTsLnEV7+6YRObe/H559up1DJmbDCa1rkvsAFDtEtN9bRP4AI71WH9CKt9L/
         iE0XFyH667MqEnQmwxzQCCmUUTMM8iBCkJMgUZOJ5YAejBiBPpFn9nER65P3qSkLDgwk
         jDbA==
MIME-Version: 1.0
X-Received: by 10.60.52.208 with SMTP id v16mr37781579oeo.15.1409731249557;
 Wed, 03 Sep 2014 01:00:49 -0700 (PDT)
In-Reply-To: <140903003158.ZM15646@torch.brasslantern.com>
References: <CANRundnVwrDtsL2DKMAuYpraGQx3SQRjsO-BCcwBo5tAGrewuA@mail.gmail.com>
	<140903003158.ZM15646@torch.brasslantern.com>
Date: Wed, 3 Sep 2014 16:00:49 +0800
Message-ID: <CANRundndRjwtWqAa+s9=wy-yzGydgf_sL9csfigu0MfZXJcXyA@mail.gmail.com>
Subject: Re: Z-Shell breaks im-config configuration scripts, making input
 method malfunction
From: =?UTF-8?B?VmRyYWdvbu+8tuWtl+m+jQ==?= <vdragon.taiwan@gmail.com>
To: Bart Schaefer <schaefer@brasslantern.com>
Cc: zsh-workers@zsh.org
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Thanks for pointing out, I expected Zsh behaves different than Bash
but wasn't knowledgeable enough to find the issue.  I've patched KDM's
script to avoid this issue already but I'll try your workaround just
for double check, thanks!

=EF=BC=B6=E5=AD=97=E9=BE=8D(Vdragon)<Vdragon.Taiwan@gmail.com>

2014-09-03 15:31 GMT+08:00 Bart Schaefer <schaefer@brasslantern.com>:
> On Sep 3,  2:53pm, Vdragon0xFF360x5B570x9F8D wrote:
> }
> } Although it seems to be KDM's bug that uses my default shell(Zsh) to ru=
n
> } the XSession script, it seems abnormal for Zsh to fail at that script a=
lso,
> } thus here's the bug report.
>
> Unfortunately, the script breaks for an entirely normal reason as far
> as zsh is concerned:  It uses a glob pattern that doesn't match any
> files.  The script needs "setopt no_nomatch" to run correctly in zsh
> (among possibly other problems, but that's the one that shows up in
> your trace output).
>
> As a workaround, you could add "setopt no_nomatch" to your ~/.zshenv
> file, and then "setopt nomatch" again in ~/.zshrc or ~/.zlogin.