From: Karel Zak <kzak@redhat.com>
To: Boris Egorov <egorov@linux.com>
Cc: util-linux@vger.kernel.org
Subject: Re: [PATCH] bash-completion: handle comma-separated options in findmnt
Date: Tue, 2 Jun 2015 12:34:51 +0200 [thread overview]
Message-ID: <20150602103451.GG7285@ws.net.home> (raw)
In-Reply-To: <1433008876-8622-1-git-send-email-egorov@linux.com>
On Sun, May 31, 2015 at 12:01:16AM +0600, Boris Egorov wrote:
> So, I discovered a way to complete comma-separated options. This
> solution can become messy when you have too many values listed.
Yes, it's little bit messy, but it's still better than nothing :-)
> Similar fixes for other utils follow if this one will be merged.
I have no objections, go ahead.
Karel
--
Karel Zak <kzak@redhat.com>
http://karelzak.blogspot.com
prev parent reply other threads:[~2015-06-02 10:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-30 18:01 [PATCH] bash-completion: handle comma-separated options in findmnt Boris Egorov
2015-06-02 10:34 ` Karel Zak [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=20150602103451.GG7285@ws.net.home \
--to=kzak@redhat.com \
--cc=egorov@linux.com \
--cc=util-linux@vger.kernel.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