-
Notifications
You must be signed in to change notification settings - Fork 39
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Make search
the default subcommand
#12
Comments
Sounds great to me. Actually as I added the |
👍 |
Still thinking that This would ensure consistency with |
Good point, and I agree with you. Bad example on my part. Let me rephrase that second one...
|
Wow @AliSoftware sweating the details! |
@irrationalfab always 😉 |
Is it weird that a valid search this week (e.g. I'm trying to think of another unix command that follows this pattern (first positional arg can be a named subcommand if it exists or input to the default command) and I can't think of one off the top of my head. @AliSoftware, you've got me overthinking the details now! 😄 |
Agreed, I was thinking the same thing. Maybe setting This gives more and more credit to @irrationalfab 's suggestion of having a separate I vote for
hehehe |
@AliSoftware Sounds good. |
Done! (new commits in #13) |
With @AliSoftware adding the
search
subcommand we could make that the default and change the behavior ofsearch
to list all the plugins unless you pass in an optional regex to search with.pod plugins
would list out all the pluginsand
pod plugins neonichu
would list any plugins that @neonichu authors.Thoughts?
The text was updated successfully, but these errors were encountered: