Bug 218511

Summary: shells/fish No matches for wildcard '/usr/ports/(commandline -ct)*/'
Product: Ports & Packages Reporter: Martin Filla <freebsd>
Component: Individual Port(s)Assignee: Alan Somers <asomers>
Status: Closed FIXED    
Severity: Affects Only Me CC: freebsd
Priority: --- Flags: bugzilla: maintainer-feedback? (asomers)
Version: Latest   
Hardware: i386   
OS: Any   

Description Martin Filla 2017-04-09 18:03:02 UTC
Hello i wanted use portmaster for virtualbox 
but fish shell crash.

sudo portmaster virtualbox_readmeNo matches for wildcard '/usr/ports/(commandline -ct)*/'.
/usr/local/share/fish/functions/__fish_complete_subcommand.fish (line 2):         ls -d /usr/ports/(commandline -ct)*/                 | sed -E -e 's#/usr/ports/##' -e 's#/+#/#' -e 's#([^/]+/[^/]+).*#\1#'
                                                                                        ^
in command substitution
	called on line 0 of file /usr/local/share/fish/functions/__fish_complete_subcommand.fish

in command substitution
	called on line 0 of file /usr/local/share/fish/functions/__fish_complete_subcommand.fish

in function '__fish_complete_subcommand'
	called on line 5 of file /usr/local/share/fish/functions/__fish_complete_subcommand_root.fish

in function '__fish_complete_subcommand_root'
	called on standard input
	with parameter list '-u -g'

in command substitution
	called on standard input
Comment 1 Martin Filla 2017-04-09 18:05:51 UTC
fish, version 2.5.0
Comment 2 Alan Somers freebsd_committer freebsd_triage 2017-04-10 04:46:45 UTC
Not a FreeBSD bug, but an upstream bug.  BTW, the shell doesn't crash.  Despite the error message, it continues working just fine.  I opened an upstream bug for it.
https://github.com/fish-shell/fish-shell/issues/3949
Comment 3 Alan Somers freebsd_committer freebsd_triage 2017-04-11 20:31:11 UTC
BTW I fixed this upstream.  It will be included in fish 2.6.0.
Comment 4 Martin Filla 2017-04-11 20:42:46 UTC
Thanks you very much.
Comment 5 Alan Somers freebsd_committer freebsd_triage 2017-05-18 18:13:55 UTC
*** Bug 219386 has been marked as a duplicate of this bug. ***