From: Oliver Kiddle <okiddle@yahoo.co.uk>
To: dana <dana@dana.is>
Cc: Zsh workers <zsh-workers@zsh.org>
Subject: Re: [BUG/RFC] IPv6 host:port completion needs work
Date: Mon, 11 Feb 2019 18:25:29 +0100 [thread overview]
Message-ID: <56368-1549905929.995530@tv9I.-ykB.1CRi> (raw)
In-Reply-To: <B48BBD05-1944-4106-B65D-82DD6F761523@dana.is>
On 5 Feb, dana wrote:
> I could update _hosts itself to take an option telling it to do two compadd
> passes, one with -p\[ -s\] (for hosts matching *:*) and one without (for the
> rest). That's similar in concept to what i did to _bind_addresses for
> workers/43207. But is that the best way? Am i overlooking something?
Yes, the approach taken in _bind_addresses where -b indicates that
IPv6 addresses need quoting with square brackets seems good to me.
_hosts_ports could also accept it and pass it on down.
Oliver
prev parent reply other threads:[~2019-02-11 17:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-05 20:01 dana
2019-02-11 17:25 ` Oliver Kiddle [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=56368-1549905929.995530@tv9I.-ykB.1CRi \
--to=okiddle@yahoo.co.uk \
--cc=dana@dana.is \
--cc=zsh-workers@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).