This is the first I have heard anybody having this problem besides me. And I have been having it for weeks and weeks if not months. I got so aggravated that I started typing nasty notes into the bug reporting box/tool.
I am going to go cancel my subscription and start migrating to another tool. Thanks for your suggestions.
So now with version 6.8.5, everytime you launch a fill-in snippet, the damn main TextExpander window opens too. Maybe we should be hoping Smile sells TextExpander also.
When reading this thread I can’t help but thinking “thanks to our great friends at Smile”.
OTOH, I used TE myself long ago, and back then it worked fine. Moved over to aText (mainly because of price) and never looked back. Advantage of aText and (I assume) Typinator over Alfred is that you can have snippets per application.
I’m pleased I found this thread. I have just cancelled by TE subscription and gone to aText which looks like it does the job fine.
As well as the problems with TE crashing, I have had issues with a snippet that contained an AppleScript to get current IP - sometimes works, sometimes doesn’t. Probably related?
My problems started when I got my M1 MacBook but happen on both M1 and Intel iMac. Possibly there was a rewrite for Silicon which went wrong?
I just went through the process of downloading the Typinator trial, and exporting my TE snippets over, to have a go.
Typinator is almost there for me – but unfortunately (and quite understandably), some of my more complex TE macros – that have many inline text additions around dropdown/fill-in’s and the like – didn’t make the transition cleanly. To be clear: this is not a criticism of Typinator, just making the point that whereas 90% of it seemed to transfer neatly, the more heavyweight macros did not.
Based on my TE account, think I am due the next annual payment sometime in October. I will hopefully find the time between then and now, to get those bigger snippets working.
Oh – and for my part – TE has been getting incredibly laggy of late. Not entirely sure what is running interference, but frequently have quite a few seconds between a trigger being initiated, and the snippet being expanded – which obviously defeats much of the purpose of text expansion in the first place, if I am losing seconds each time I expand certain snippets, waiting for TE to catch up…
It is really annoying. Guess time will tell regarding whether it is annoying enough…
Yes, you sort of have to redo your fill in macros in Typinator, but I think it can do everything TE does. (Of course, it’s up to you to see if it’s worth the hassle depending on how many you have)
seeing lots of tweets the past two days about TextExpander crashing and not expanding snippets as expected. I hope the best TE coder wasn’t also on the PDFPen team…
Oh thank god I saw this thread. I thought I was going crazy. So frustrating, but thank you all for the suggestion of clicking on the dock icon when the pop up window wasn’t showing up. I am going to give them some more time before jumping, but I am going to continue watching this thread.
For better or worse, my history is to cut a company a lot of slack IF they are communicating with their users. If not, then I have to do what’s right for me.
If Smile was any kind of organized company, they would be communicating with their users. Can they tweet that they acknowledge the issues and are working on them? No, here are some of their latest “textexpander” tweets
Smile seem to be a tone-deaf company. It’s weird. They’ve been around forever, and you their software isn’t great. They spend a bucketload on marketing, but their social media marketing is hopeless. Their software is ugly but has filled niches for a long time.
Now they sell PDF Pen, which either means they are going to focus more on TextExpander, or try to sell it too and close up shop.
