zsh-users
 help / color / mirror / code / Atom feed
From: Aaron Davies <agdavi01@louisville.edu>
To: zsh-users@sunsite.dk
Subject: Re: Suppressing "no matches found" Glob Message?
Date: Mon, 28 Jun 2004 18:53:48 -0400	[thread overview]
Message-ID: <04955BBD-C956-11D8-ADCC-000A95EDC31A@louisville.edu> (raw)
In-Reply-To: <20040628085300.GA1443@DervishD>

On Jun 28, 2004, at 4:53 AM, DervishD wrote:

> Aaron Davies <agdavi01@louisville.edu> dixit:
>
>>> Yes, change your pattern to, for example 'ls **/*(.N)'. The 'N'
>>> means 'set option NULL_GLOB' for this pattern. This removes the
>>> error.
>>
>> NULL_GLOB seems to remove the pattern entirely, so it no longer finds
>> plain files only.
>
> NULL_GLOB makes zsh deleting the pattern if no match is found,
> but happens that 'ls', without options, prints all files and dirs in
> the current directory.
>
>> I think what I want may be NOMATCH instead, but I
>> can't figure out a code to set that. Is there one?
>
> Don't know, but you don't want NOMATCH set: it *prints* an error
> if a match is not found. If you unset it, what you are going to have
> is the pattern as-is, so 'ls' will complain saying that '**/*(.)'
> doesn't exist.

That wouldn't be so bad, actually; I could redirect that error to 
/dev/null. So, does anyone know how to set that option in a pattern?
-- 
Aaron Davies
agdavi01@louisville.edu


  reply	other threads:[~2004-06-28 22:54 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-27  2:39 Aaron Davies
2004-06-27 10:42 ` DervishD
2004-06-27 22:50   ` Aaron Davies
2004-06-28  8:53     ` DervishD
2004-06-28 22:53       ` Aaron Davies [this message]
2004-06-29  8:52         ` DervishD
2004-06-29  9:56           ` Lloyd Zusman
2004-06-29 10:41             ` DervishD
2004-06-29 16:12       ` Bart Schaefer
2004-06-29 16:34         ` DervishD
2004-06-29 23:04         ` Aaron Davies
2004-06-30 10:10           ` Bart Schaefer
2004-07-01  4:28             ` Aaron Davies
2004-06-27 22:52   ` Aaron Davies

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=04955BBD-C956-11D8-ADCC-000A95EDC31A@louisville.edu \
    --to=agdavi01@louisville.edu \
    --cc=zsh-users@sunsite.dk \
    /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).