zsh-workers
 help / color / mirror / code / Atom feed
From: Peter Stephenson <p.stephenson@samsung.com>
To: <zsh-workers@zsh.org>, Varshith Sreeramdass <varshiths@cse.iitb.ac.in>
Subject: Re: [Bug] Use of [] in python package names
Date: Wed, 13 Mar 2019 09:37:03 +0000	[thread overview]
Message-ID: <1552469823.4642.3.camel@samsung.com> (raw)
In-Reply-To: <9049d434-6c89-e5a0-cb27-e0a56f42eabb@cse.iitb.ac.in>

On Wed, 2019-03-13 at 11:46 +0530, Varshith Sreeramdass wrote:
> I use zsh 5.7.1.
> 
> To install spacy with GPU support, the command involved is
> 
>     /$ pip install -U spacy[cuda100]/
> 
> While it works perfectly on bash, zsh throws the following error.
> 
> /        zsh: no matches found: spacy[cuda100]/
> 
> I guess this is an issue with how [] are dealt.

Yes, the square brackets are part of file pattern matching ("globbing",
in the shell jargon) syntax, so need quoting.  Zsh just happens to be
more consistent about this than bash in the default mode (either it's a
pattern that needs to match something or it isn't and doesn't).  It's
not a bug.

If you want the bash behaviour --- where it simply ignores the pattern
if it doesn't match --- you can put

setopt nonomatch

in you ~/.zshrc.

I don't know what the oh-my-zsh attitude to this option is, but I'm
pretty sure there's no implication there of complete bash compatibility
out of the box.

pws





      reply	other threads:[~2019-03-13  9:37 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20190313061733epcas4p1e506fc7c5d41b7e22f6fdd44b8771da7@epcas4p1.samsung.com>
2019-03-13  6:16 ` Varshith Sreeramdass
2019-03-13  9:37   ` Peter Stephenson [this message]

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=1552469823.4642.3.camel@samsung.com \
    --to=p.stephenson@samsung.com \
    --cc=varshiths@cse.iitb.ac.in \
    --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).