
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. 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. In the last few days though, the application that has enabled this mode has become loginwindow. Secure input prevents key–logging malware from recording applications, but it also prevents snippet expansion.įair enough, the benefit outweigh the potential inconvenience.

Without it, I feel like I’ve been thrust in front of a shell and asked to draw a picture.

Loginwindow has disabled textexpander code#
My beloved shortcuts activate autocompletions, expansions, tedious code and markup boilerplate, forms and even fire Perl scripts. Along with Quicksilver and nvALT, its functionality is now triggered from muscle memory.
