This applies to many different snippets I've created - as an example:
I've made "lmk" expand to "let me know" but since snippets are not-case sensitive, I have to make an additional separate snippet to make "/lmk" expand to "Let me know" - since a snippet of "Lmk" conflicts with "lmk".
Unless/until TB creates a feature like TextExpander where it automatically adjusts to the case used upon input, will TB at some point make snippets case sensitive? is that TE feature being considered for TB?
Thanks!
Hi @erosenblatt Welcome to the forum! 
Have you tried our Capitalize command pack?
You can then set your snippet to be: {capitalize-match: Let me know} and it would match your shortcut capitalization.
Thank you, didn't know about that. My org activated the command pack, and I logged out and logged back in and restarted (and then force-restarted) the application. Still no luck -->
"lmk" and "LMK" both return the phrase "let me know"
thinking it might require a slash, I added that but unfortunately
"/lmk" and "/LMK" also both return "let me know"
Not sure what else I should try besides a reboot. Can't rn but will soon I guess...
Can you please share a screenshot of what your snippet looks like?
Aha I see now I had not set it up properly with the text inserted in that window. Thx