zsh-users
 help / color / mirror / code / Atom feed
From: Nomen Nescio <nobody@dizum.com>
To: zsh-users@zsh.org
Subject: Re: Why is this happening in zsh?
Date: Thu, 15 Mar 2012 11:13:03 +0100 (CET)	[thread overview]
Message-ID: <8982dc10f425e9b329d9c257cc586c62@dizum.com> (raw)
In-Reply-To: <20120314194923.39145cd3@pws-pc.ntlworld.com>

Peter Stephenson <p.w.stephenson@ntlworld.com> wrote:

> On Wed, 14 Mar 2012 19:59:02 +0100 (CET)
> Anonymous <remailer@foo.asia-king.co.uk> wrote:
> > fossil --ignore *.class
> > zsh: no matches found *.class
> 
>   setopt nonomatch
> 
> fixes this.
> 
> If you are generally speaking expecting bash-like behaviour you might
> want to read the zshoptions manual page and note in particular options
> that are marked <S> (on in sh emulation) or <Z> (on by default in zsh
> but not necessarily emulations of other shells.

Guys: thanks very much indeed for the explanations, solutions and insights.
I have no illusions, bash and much of gnu software does things that aren't
consistent etc. I am not expecting zsh to work like bash either, if I wanted
that I would just use bash! I'm not very good with UNIX and I often miss
simple things. I do appreciate zsh works in a more uniform way. I knew there
was something about globbing but I couldn't get around it for some rsync
commands and now this. Now I think I understand a bit more. Thanks to
everyone who's answered!


  reply	other threads:[~2012-03-15 11:10 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-14 18:59 Anonymous
2012-03-14 19:29 ` Heorhi Valakhanovich
2012-03-14 23:19   ` Damien Thébault
2012-03-14 19:42 ` Stephane Chazelas
2012-03-14 19:49 ` Peter Stephenson
2012-03-15 10:13   ` Nomen Nescio [this message]
2012-03-15 18:00     ` Kyle Partridge
2012-03-16  0:11       ` Christoph (Stucki) von Stuckrad
2012-03-16  3:28       ` Benjamin R. Haskell

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=8982dc10f425e9b329d9c257cc586c62@dizum.com \
    --to=nobody@dizum.com \
    --cc=zsh-users@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).