https://bugs.kde.org/show_bug.cgi?id=474685
--- Comment #12 from Adrián Chaves (Gallaecio) <adr...@chaves.io> --- OK, so I had a `[TM]` section in $HOME/.config/lokalizerc with 3 boolean options. Removing that seemed to make the feature work again, somewhat (new strings will be marked as fuzzy even if I do not choose that). Could you all see what’s in your `[TM]` section, and see if removing that and restarting Lokalize brings the feature back for you as well. -- You are receiving this mail because: You are watching all bug changes.
