Zsh Mailing List Archive
Messages sorted by:
Re: Z-Shell breaks im-config configuration scripts, making input method malfunction
- X-seq: zsh-workers 33102
- From: VdragonＶ字龍 <vdragon.taiwan@xxxxxxxxx>
- To: Bart Schaefer <schaefer@xxxxxxxxxxxxxxxx>
- Subject: Re: Z-Shell breaks im-config configuration scripts, making input method malfunction
- Date: Wed, 3 Sep 2014 16:00:49 +0800
- Cc: zsh-workers@xxxxxxx
- 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==
- In-reply-to: <140903003158.ZM15646@torch.brasslantern.com>
- List-help: <mailto:email@example.com>
- List-id: Zsh Workers List <zsh-workers.zsh.org>
- List-post: <mailto:firstname.lastname@example.org>
- Mailing-list: contact zsh-workers-help@xxxxxxx; run by ezmlm
- References: <CANRundnVwrDtsL2DKMAuYpraGQx3SQRjsO-BCcwBo5tAGrewuA@mail.gmail.com> <140903003158.ZM15646@torch.brasslantern.com>
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!
2014-09-03 15:31 GMT+08:00 Bart Schaefer <schaefer@xxxxxxxxxxxxxxxx>:
> On Sep 3, 2:53pm, Vdragon0xFF360x5B570x9F8D wrote:
> } Although it seems to be KDM's bug that uses my default shell(Zsh) to run
> } the XSession script, it seems abnormal for Zsh to fail at that script also,
> } 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.
Messages sorted by: