Philip Brown wrote: > if "pkg search" is "Intelligent" enough to auto-expand > > basename:vim => ::basename:vim > > it should be just as equally capable of auto-expanding > > file:vim => :file::vim
Why? How do you know it's not file:::vim? What about "basename:file"? That could reasonably be "basename:file::" or "::basename:file". And given the way searching through set actions works, where the "key" is the value of the "name" attribute (so I can do a search for, say set:info.upstream-url:*gnu.org*), you can even have the key namespace overlap the action namespace. > To not do so, may justify some pretty Backus-Naur grammar definition, but > it is horrible real world user interface! I'm not saying I disagree entirely with you about needing something better than the colon-separated search argument, but given that's what we've got, there's not much more automagic we can do with the parsing. Danek _______________________________________________ pkg-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
