Development discussion of WireGuard
 help / color / mirror / Atom feed
From: Heath Borders <heath.borders@gmail.com>
To: wireguard@lists.zx2c4.com
Subject: bash_completion errors when installed with homebrew
Date: Fri, 28 Sep 2018 10:02:52 -0500	[thread overview]
Message-ID: <CAEy7hVPn++92XRedQg2OSwK0OAoqds6b15U2iHjePrWie1qrKw@mail.gmail.com> (raw)

I installed wireguard with homebrew thusly:
```
brew install wireguard-tools
```

I'm also using brew's bash completion in my `.bash_profile` and `.bashrc`:
```
if [ -f $(brew --prefix)/etc/bash_completion ]; then
  . $(brew --prefix)/etc/bash_completion
fi
```

After installing wireguard, when I open a new terminal, I see the
following errors:
```
-bash: complete: nosort: invalid option name
-bash: complete: nosort: invalid option name
```

I've traced these errors back to the following commands using `set -x`:
```
++++ complete -o nosort -F _wg_completion wg
-bash: complete: nosort: invalid option name
++++ complete -o filenames -o nosort -F _wg_quick_completion wg-quick
-bash: complete: nosort: invalid option name
```

I'm running macOS High Sierra, which runs bash version
`3.2.57(1)-release`, which doesn't support the `nosort` option. I'd
rather not upgrade my entire terminal to bash `4.4.23(1)-release` that
wireguard installs as a dependency.

I filed an issue with homebrew as well:
https://github.com/Homebrew/homebrew-core/issues/32535

Thanks!

-Heath Borders
heath.borders@gmail.com
Twitter: heathborders
http://heath-tech.blogspot.com
_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard

             reply	other threads:[~2018-10-02  3:06 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-28 15:02 Heath Borders [this message]
2018-10-02  9:46 ` Bernhard Ehlers

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=CAEy7hVPn++92XRedQg2OSwK0OAoqds6b15U2iHjePrWie1qrKw@mail.gmail.com \
    --to=heath.borders@gmail.com \
    --cc=wireguard@lists.zx2c4.com \
    /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 NNTP newsgroup(s).