From: Mikael Magnusson <mikachu@gmail.com>
To: dominik.vogt@gmx.de, Zsh Users <zsh-users@zsh.org>
Subject: Re: Brace expansion vs. TAB
Date: Sat, 7 Dec 2019 11:05:01 +0100 [thread overview]
Message-ID: <CAHYJk3T+DNbLrX2hPkbP2qtfFAYsrs9Lj1qrb59KSo2RHonR3Q@mail.gmail.com> (raw)
In-Reply-To: <20191206171812.vhynj65pxdk6woqh@gmx.de>
On 12/6/19, Dominik Vogt <dominik.vogt@gmx.de> wrote:
> (Using zsh 5.3.1 on Debian.)
>
> In a directory with c++ sources:
>
> $ ls *
> foo.cpp foo.h
>
> Now,
>
> $ grep ... *.{hpp,cpp}<TAB>
>
> Q2:
>
> What I really want to have is a simple way to get all c and c++
> filenames in a singel pattern, like
*.(hpp|cpp) or for that matter, *.[hc]pp
--
Mikael Magnusson
next prev parent reply other threads:[~2019-12-07 10:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-06 17:18 Dominik Vogt
2019-12-07 10:05 ` Mikael Magnusson [this message]
2019-12-07 12:32 ` Dominik Vogt
2019-12-07 13:23 ` Re[2]: " Manuel Presnitz
2019-12-07 13:33 ` Dominik Vogt
2019-12-08 1:23 ` Daniel Shahaf
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=CAHYJk3T+DNbLrX2hPkbP2qtfFAYsrs9Lj1qrb59KSo2RHonR3Q@mail.gmail.com \
--to=mikachu@gmail.com \
--cc=dominik.vogt@gmx.de \
--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).