From: Kyle Meyer <kyle@kyleam.com>
To: Eric Wong <e@80x24.org>
Cc: meta@public-inbox.org
Subject: Re: RFC: lei q --include/-I and similar switch names
Date: Tue, 26 Jan 2021 21:04:18 -0500 [thread overview]
Message-ID: <87sg6n16fx.fsf@kyleam.com> (raw)
In-Reply-To: <20210125073347.GA15401@dcvr>
Eric Wong writes:
> "add-external" sometimes feels like an unnecessary burden
> for a one-off search, so it'd be nice to be able to search
> an external once, or exclude certain externals.
>
> I'm set on supporting "-I$DIR_OR_URL" since that's common
> command-line usage for gcc/clang/tcc, perl, ruby to include
> extra search paths for headers/modules.
Sounds very useful.
> --exclude is naturally the opposite of --include, and I don't
> know if --exclude needs a short name. "-v" (like "grep -v")
> isn't available, but maybe "-X" works, since it's something we
> can't pass from the CLI to curl. We're not passing "-x" to
> curl, either, but we pass "--proxy" through, of course.
My two cents: I think it'd be okay to leave --exclude without a short
name...
> I don't know if "--only" is a good name and don't know of any
> common tools with similar functionality (but I know very little
> in general :x). "--exclusive" would be confusing with
> "--exclude" and require more typing even with tab-completion.
> If we use "--only", then we can use -O for --only since we can't
> forward -O to curl, either...
... and --only/-O sounds good to me.
prev parent reply other threads:[~2021-01-27 2:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-25 7:33 RFC: lei q --include/-I and similar switch names Eric Wong
2021-01-27 2:04 ` Kyle Meyer [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
List information: https://public-inbox.org/README
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87sg6n16fx.fsf@kyleam.com \
--to=kyle@kyleam.com \
--cc=e@80x24.org \
--cc=meta@public-inbox.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.
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 read-only IMAP folder(s) and NNTP newsgroup(s).