Skip to content
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

commands should use subject-verb format #42

Open
jeremy-w opened this issue May 28, 2013 · 2 comments
Open

commands should use subject-verb format #42

jeremy-w opened this issue May 28, 2013 · 2 comments

Comments

@jeremy-w
Copy link
Contributor

Switch to a subject-verb command-subcommand structure like wry file upload $PATH and wry user follow $USER. This format is mostly orthogonal to the existing system, so the current commands would become aliases for the full version, e.g. wry upload becomes wry file upload during an argument preprocess step.

This would also make #36 very straightforward!

@hoop33
Copy link
Owner

hoop33 commented Jun 6, 2013

I've thought about this one and am not sold. It would help on namespacing the verbs, but I'm not sure how big an issue that is. This approach would require more typing, so the upside would need to be clear. What are your thoughts on what problems this would solve?

@jeremy-w
Copy link
Contributor Author

jeremy-w commented Jun 6, 2013

More typing can be solved in a heavy-handed way via command aliases. It's a shell program, so alias wp='wry post new' is available to the user at all times and works without requiring any in-app code.

The app can avoid the need for anyone to do that by using the minimal-unique-string approach to matching commands as demonstrated in LLDB and GDB, which allows you to abbreviate "frame variables" to "fr var" and "breakpoint list" to "br l".

If the plan is to have shell functions to provide command completion anyway, it's easy to seed default aliases, and typing length is shortened greatly by use of the <TAB> key.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants