That's an approach I'll look into someday. I never thought of storing text expansions in variables until it was mentioned upthread. If you have extensive needs, or thousands of snippets to import from somewhere, then use Typinator. So, my recommendation is that if you have light-to-moderate text expansion needs, use KM, or at least start with KM. Some others I can't remember right now.However, there are some use cases where KM might be preferred:.It is not designed to handle thousands of snippets (which means Macros in KM).It may well be fine for many users, many use cases.By comparison, is a good, but light-weight text expander.There are many 3rd party Typinator sets available that you can subscribe to or import into your local storage.It has a great search auto-completion feature to help you choose an abbreviation to expand.It is very easy to add a new snippet (abbreviation) to Typinator.is a high-end, industrial-strength text expansion tool that can easily handle thousands of snippets.Most of my text-expansions are in Typinator, but I do have a few in KM. The Macro is the container that stores your text.įirst, I have to say that I have, and frequently use, both of these great apps. Store the resultant text in a Local Variable. But in most text-expansion cases, you don't even need Global Variables.Store your permanent plain text in KM Global Variables.They are only needed to store images, rich text, and objects.They offer no advantage for storing and using plain text.So let's start with KM "Named Clipboards" I don't understand your connection between KM "Named Clipboards" and Typinator. In which situations would you use a named clipboard as opposed to a sophisticated ‘text’ expander like Typinator?
0 kommentar(er)
