On Tue, Sep 20, 2016 at 3:44 PM Noam Postavsky <
address@hidden> wrote:
Check for text properties and/or overlays on the affected region with C-u C-x =
Thanks. I should have thought of that when that bug happened! C-u C-x = gives the text properties at point.. it didn't occur that I put the point in the region that shows that highlight, hover the mouse over that region and then do C-u C-x =. I'll do so next time that happens :)
I faked a typo in a string, put the point in there and hovered the mouse to get the overlay. Then C-u C-x = gives:
Character code properties: customize what to show
name: LATIN SMALL LETTER N
general-category: Ll (Letter, Lowercase)
decomposition: (110) ('n')
There are 2 overlays here:
From 32334 to 32339
category nil
modification-hooks [Show]
From 32334 to 32339
evaporate t
face flyspell-incorrect
flyspell-overlay t
help-echo "mouse-2: correct word at point"
keymap [Show]
mouse-face highlight
There are text properties here:
face font-lock-string-face
fontified t
I'll post back my findings when that bug re-appears. If flyspell is causing it, disabling flyspell-mode should get rid of that highlight..
> If so, what major/minor mode provides that functionality? From a
> position of ignorance, my first thought is that it seems related.
I was wondering about this too.
I'll update this thread with new findings.