zsh-users
 help / color / mirror / code / Atom feed
From: Peter Stephenson <p.stephenson@samsung.com>
To: Zsh Users <zsh-users@zsh.org>
Subject: Re: Filtering argument lists (e.g. for grep)
Date: Mon, 07 Dec 2015 11:23:54 +0000	[thread overview]
Message-ID: <20151207112354.5d24de89@pwslap01u.europe.root.pri> (raw)
In-Reply-To: <20151207105622.GA18231@linux.vnet.ibm.com>

On Mon, 7 Dec 2015 11:56:22 +0100
Dominik Vogt <vogt@linux.vnet.ibm.com> wrote:
> For some commands, there are some file patterns that I never want
> to pass to the command (unless explicitly stated otherwise).  For
> example, grep'ing should normally ignore backup and ChangeLog files
> 
>  *ChangeLog*
>  *~
>  \#*
> 
> Maybe grep is a bad example because this can be done with the
> --exclude= option.  But could zsh help filtering the names
> generated by globbing in a more general way so that I could write
> 
>   $ <foo> *
> 
> and have zsh automagically filter the results of the * (not
> everywhere; only for commands that have this feature enabled) so
> that the non-matching names are not passed to the command in the
> first place?

You could use a global alias, e.g.

alias -g '@*'='*~(*\~|\#*|ChangeLog)'

Ig you want that first * to be something more flexible you can use a
glob qualifier.

  gi () {
    [[ $REPLY != (*\~|\#*|ChangeLog) ]]
  }

and use

  <foo> *(+gi)

pws


  parent reply	other threads:[~2015-12-07 11:24 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-07 10:56 Dominik Vogt
2015-12-07 11:18 ` Dominik Vogt
2015-12-07 11:23 ` Peter Stephenson [this message]
2015-12-07 11:39   ` Dominik Vogt
2015-12-07 11:56     ` Nikolay Aleksandrovich Pavlov (ZyX)
2015-12-07 12:03     ` Nikolay Aleksandrovich Pavlov (ZyX)
2015-12-07 12:06       ` Nikolay Aleksandrovich Pavlov (ZyX)
2015-12-07 12:58         ` Nikolay Aleksandrovich Pavlov (ZyX)

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=20151207112354.5d24de89@pwslap01u.europe.root.pri \
    --to=p.stephenson@samsung.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).