TextExpander reporting that secure input is preventing expansion

I swear by TextExpander. Along with Quicksilver and nvALT, its functionality is now triggered from muscle memory. My beloved ;shortcuts activate autocompletions, expansions, tedious code and markup boilerplate, forms and even fire Perl scripts. Without it, I feel like I’ve been thrust in front of a shell and asked to draw a picture.

(As I wrote that, I could hear the voices of a thousand pedants shrieking that there are ways to draw in a shell window, from box characters to ASCII art to cowsay to figlet to launching graphical tools. Smart–arses may even decry shells don’t need further decorating, as the sea creatures already did such a beautiful job. And yet, I still wrote it. Maybe I’m a blogging masochist).

Trouble in paradise

Perhaps the most common error I get with the tool, besides occasional clipboard dumps, is Disabled by Secure Input. Unfortunately, what used to be a once–in–a–month occurrence has now been happening almost hourly.

From the error message:

Secure event input is enabled when you type in a password field (•••) and in other instances by certain applications. Secure input prevents key–logging malware from recording applications, but it also prevents snippet expansion.

Fair enough, the benefit outweigh the potential inconvenience. In the last few days though, the application that has enabled this mode has become loginwindow. Smile’s online docs explain:

When TextExpander tells you the name of the application that has enabled secure input, it’s giving you a “best guess” that’s sometimes inaccurate. When TextExpander reports that “loginwindow” has enabled secure input, it’s likely that TextExpander can’t quite tell which application has enabled secure input, so instead it’s showing that application’s “ancestor, ” loginwindow. This can also happen when OS X itself has left secure input enabled after you’ve logged in, or after you’ve entered your password to wake the computer from sleep or from screensaver.

Where do I even begin?

In the New Normal where applications routinely update themselves in the background, Mac App Store updates occur overnight and others inform us they need updating upon launching, it could be almost any application on my machine that’s triggering this Secure Input mode and not gracefully turning it off again. I’m hoping its not one of the Important Programs people use; physically impaired people who use OS X’s accessibility options must be even more frustrated than me.

For now, I’m learning to appreciate all that TextExpander saves me from doing. Typing all this stuff out manually again feels more archaic than using a shell to draw pictures.