Skip to content

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

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

UX: Maybe subcommands should be the 1st argument instead of options #30

Closed
noncombatant opened this issue Dec 28, 2019 · 2 comments
Closed

Comments

@noncombatant
Copy link
Contributor

noncombatant commented Dec 28, 2019

This is an arguable style matter. But I find the 'modern' style of go and git a bit easier to use. E.g.:

age decrypt options...

age encrypt options...

Then you'd get rid of -d, --decrypt, and -r and -p would no longer implicitly mean "encrypt". It'd be explicit.

@noncombatant
Copy link
Contributor Author

I should also add: This allows the possibility of combining age and age-keygen, by creating an age keygen subcommand. Then there'd only be 1 binary, and possibly more code sharing.

@ovalseven8
Copy link

See #22

Repository owner locked and limited conversation to collaborators Apr 19, 2021

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants