Be apply define snippet shortcuts that are case sensitive (e.g. /go is different from /GO and /Go).
Just adding my thoughts from another post and up-voting.
Although the "/" has it's use, I would like to suggest logic control (see the last item in this post) which gives the user full control of whatever they want to do.
I know Microsoft Word adjusts automatically for the start of a sentence.
Or you could go with WTH => "WHAT THE HECK", Wth => "What the heck" and wth => "what the heck"
I would also be interested in full user control using something like an IF statement check on the text input characters:
IF {input = lower case} "what the heck"
ELSEIF [input = upper case} "What the heck"
ELSEIF {input = sentence case} WhAt ThE HeCk
ENDIF
IF {input = "wth"} "what the heck"
ELSEIF [input = "WTH"} "What the heck"
ELSEIF {input = "WtH"} "WhAt ThE HeCk"
ELSEIF {input ="Wth"} "WHAT THE HECK"
ENDIF
This would be really, really useful. I'd like to see a simple option which modifies the shortcut based on the case. For me, even just having the following behaviour would be fine:
Mtfte => Many thanks for the email
mtfte => many thanks for the email
In addtion to that; even if this isn't possible, it would be good if I could at least both define those separately (even though it would be a pain). At the moment, if you do this, they are classed as "conflicting shortcuts".
This feature was added in a recent release. An example is here:
This is fairly complex for wanting to insert the same word, one capitalized, one not. That's all I'm trying to do. "/Unf" typing "Unfortunately" vs "/unf" typing "unfortunately"
Amazing work on this btw. Thanks!
Hi, and welcome to the forum Elise! 
Agreed! We're working on higher level components that will implement common use cases like this to make them easier to use.
Another example of something like this we want to simplify is randomly selecting a piece of text. E.g. starting a message with "Howdy", "Hi", or "Hey there" and randomly choosing one each time you use the snippet.
That would be awesome!
Quick update to this old but popular feature request. Both the items above were implemented via a new feature called command packs.
- Matching case of the text to the snippet shortcut case: use the capitalize command pack, and
- Choosing one random text from a list of texts: use the randomize command pack
We just bulk imported our snippets from TextExpander and were surprised to find that Text Blaze shortcuts are not case sensitive. We have a folder of snippets that are "auto-corrects" for our company brand guidelines. This lack of case sensitivity in shortcuts broke a few of the auto-corrects as a result. Though the case-sensitive insertion option here is viable, it is a awfully heavy workaround for simply making shortcuts case sensitive.
Hi again @Alex_Armstead and welcome to the forum! ![]()
Thanks for your feedback. I understand in your use case it would make sense to have the shortcuts be case-sensitive. Right now we don't have any updates to share on this feature request. When we do, we'll update the thread accordingly.
I find that way of creating case-sensetive snippets, a bit buggy, but also very slow to create, and personally, I'd much prefer a global option (configured in either the main options area for Text Blaze, or in a separate advanced settings area), so that if a user who would prefer to use the:
Mtfte => Many thanks for the email
mtfte => many thanks for the email
..as outlined by @Tom_Kerswill could do so. I know it's largely down to personal taste & preference, but it makes it a lot quicker to use the approach outlines by @Tom_Kerswill, and it's a lot easier to remember, I think.
The method used in the new feature as posted by @scott would be great for some people, but it would be so nice if the @Tom_Kerswill was at least an available option to users like me and @Tom_Kerswill
I will really look forward to the higher-level case sensitive snippets method if you're talking about the method Tom have just described @scott and I hope I got that right?
Hi Jon, Thanks for the feedback!
You mentioned things were a bit buggy for you. Can you elaborate more? What issues did you run into?
Also, are you using the capitalize command pack? It should be a lot faster than writing out the {if} statements by hand.