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
Is your feature request related to a problem? Please elaborate.
It seems unintuitive that snippets cannot be invoked case-insensitively whilst commands can - all the plugin sub-commands even coerce the snippet name to be lower-case such that ?snippet FOO is equivalent to ?snippet foo.
?snippet add FOO followed by ?FOO doesn't even work since a snippet by the name "foo" is added.
Describe the solution you'd like
I'd like for ?FOO to be equivalent to ?Foo or ?foo or any other combination of cases for that matter.
Does your solution involve any of the following?
Logviewer
New config option
Describe alternatives you've considered
Making a plugin with a custom process_commands.
Who will this benefit?
Everyone who uses snippets. I find myself accidentally capitalizing the first letter of the snippet accidentally only to have it not work.
Additional Information
No response
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please elaborate.
It seems unintuitive that snippets cannot be invoked case-insensitively whilst commands can - all the plugin sub-commands even coerce the snippet name to be lower-case such that
?snippet FOO
is equivalent to?snippet foo
.?snippet add FOO
followed by?FOO
doesn't even work since a snippet by the name "foo" is added.Describe the solution you'd like
I'd like for
?FOO
to be equivalent to?Foo
or?foo
or any other combination of cases for that matter.Does your solution involve any of the following?
Describe alternatives you've considered
Making a plugin with a custom
process_commands
.Who will this benefit?
Everyone who uses snippets. I find myself accidentally capitalizing the first letter of the snippet accidentally only to have it not work.
Additional Information
No response
The text was updated successfully, but these errors were encountered: