You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
DESCRIPTION:
Generate a new password of the specified length, optionally with no symbols. Alternatively, a xkcd style password can be generated (https://xkcd.com/936/). Optionally put it on the clipboard and clear clipboard after 45 seconds. Prompt before overwriting existing password unless forced. It will replace only the first line of an existing file with a new password.
I suggest to change it to something more succinct and along the lines of:
Dialog to generate a new password and write it into a new or existing secret. By default, the new password will replace the first line of an existing secret (unless it's a key-value-pair?). Supports options of pwgen and show listed below.
[...]
Problem b
PS > gopass generate example -c
How long should the password be? (q to abort) [24]:
✅ Password for entry "example:-c" generated
Not printing secrets by default. Use 'gopass show example:-c' to display the password.
Error: failed to set key "-c" of "example": entry is not in the password store
(Note: This Error message is mostly helpful)
The intention was to generate a password for a new secret, and to immediately copy it to the clipboard.
The operation fails because the -c comes after an argument. This may be inobvious to a user (me), as option and argument are words with very similar meaning. Listing the possible arguments in the the Usage would mitigate this
PS > gopass generate Account/example.com 16 -c results in
Error: password length must be a number
Again, an option follows an argument. So gopass attempts to generate a password for the key 16 into Account/example.com and complains about -c not being a number.
It would be very helpful if gopass informed the user of what generate recognized as arguments, if any were provided.
This commit adds the ArgsUsage to most commands to better illustrate the
intended usage of the different commands.
RELEASE_NOTES=[ENHANCEMENT] Add better usage instructions
Fixesgopasspw#1911
Signed-off-by: Dominik Schulz <dominik.schulz@gauner.org>
This commit adds the ArgsUsage to most commands to better illustrate the
intended usage of the different commands.
RELEASE_NOTES=[ENHANCEMENT] Add better usage instructions
Fixes#1911
Signed-off-by: Dominik Schulz <dominik.schulz@gauner.org>
kpitt
pushed a commit
to kpitt/gopass
that referenced
this issue
Jul 21, 2022
This commit adds the ArgsUsage to most commands to better illustrate the
intended usage of the different commands.
RELEASE_NOTES=[ENHANCEMENT] Add better usage instructions
Fixesgopasspw#1911
Signed-off-by: Dominik Schulz <dominik.schulz@gauner.org>
Summary
The text shown by command
gopass help generate
isProblem a
gopass help generate
better: Generate a new password and write it into a secret.
See below
I suggest to change it to something more succinct and along the lines of:
Dialog to generate a new password and write it into a new or existing secret. By default, the new password will replace the first line of an existing secret (unless it's a key-value-pair?). Supports options of
pwgen
andshow
listed below.Problem b
(Note: This Error message is mostly helpful)
The intention was to generate a password for a new secret, and to immediately copy it to the clipboard.
The operation fails because the
-c
comes after an argument. This may be inobvious to a user (me), as option and argument are words with very similar meaning. Listing the possible arguments in the the Usage would mitigate thisSay:
gopass.exe generate [command options] [secret [key [length ...?]]]
Problem c
PS > gopass generate Account/example.com 16 -c
results inError: password length must be a number
Again, an option follows an argument. So gopass attempts to generate a password for the key
16
intoAccount/example.com
and complains about-c
not being a number.It would be very helpful if gopass informed the user of what
generate
recognized as arguments, if any were provided.Environment
Additional context
The text was updated successfully, but these errors were encountered: