Open a C++ (*.cpp) or C (*.c) file (I couldn't replicate using a plain *.txt file) with two or more "pages" of code and enable Tools > Spelling > Automatic Spell Checking. Locate a word that is underlined red (i.e. flagged for incorrect spelling) among comments or strings in the source code. Right click on the word and select Spelling > Add to Dictionary. The word will no longer be underlined, but if the word scrolls out of view and then scrolls back into view, it will be underlined once again. If I restart KDevelop, the word is recognized as correct with no issues.
This is happening to me too using Kate. I am using Markdown. Add a word to dictionary, underline disappears, Scroll down, scroll back (or save and reopen) and underline reappears! Kate version 17.12.3,Linux (x86_64) release 4.15.0-24-generic Looked in my ~.aspell.en.pws and the words are being added in. But seem not to be taken into account when spelling the document!
After investigating more I notice that I had the dictionary set to en_GB with -ise endings. When I switched it to en in Kate's spelling settings my personal dictionary worked perfectly.
Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version? If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!