Placeholder descriptions #194
Unanswered
georgeharker
asked this question in
Ideas
Replies: 1 comment
-
|
Hi! Thanks for sharing your idea. I think adding support for either a user-configurable array of placeholder strings ( Uncertain if it's something I'd like to support. + It's neat
- The first one in a given expansion would never be seen (except when listing available abbreviations)
+ Your reason makes sense
- Helping understand expanded commands hasn't been part of the scope
? Maybe expanding scope on this way is okay?Interested to hear from others. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Really enjoying using this! Thanks!
I wonder whether it would be possible for things like %username% and %branch% to be used as placeholders such that when the expansion occurs there is a reminder of the meaning for each expand placeholder - and then subsequently overwrite with the user input?
Beta Was this translation helpful? Give feedback.
All reactions