After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 741853 - Spell Checker: 'highlight misspelled words' sometimes enabled when it shouldn't
Spell Checker: 'highlight misspelled words' sometimes enabled when it shouldn't
Status: RESOLVED FIXED
Product: gedit-plugins
Classification: Other
Component: General
3.14.x
Other Linux
: Normal normal
: ---
Assigned To: Gedit maintainers
Gedit maintainers
Depends on:
Blocks:
 
 
Reported: 2014-12-22 12:51 UTC by Sébastien Wilmet
Modified: 2019-03-23 20:54 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Sébastien Wilmet 2014-12-22 12:51:53 UTC
I don't want the 'highlight misspelled words' setting enabled, so I disable it but the next time that I open the file it is sometimes enabled again.

Steps to reproduce:
- Have two files (*.m with Matlab highlighting in my case), open them in gedit, disable the 'highlight misspelled words' setting if set.
- Close gedit
- Reopen the two files from the command line, e.g. 'gedit *.m'.

Result:
For the first file the setting is still disabled, but for the second file the setting is enabled.

When opening the files one by one from the gedit UI, the bug doesn't occur, the setting is correctly disabled.
Comment 1 Sébastien Wilmet 2015-06-07 13:26:48 UTC
I've fixed a related bug (see the commit message):

https://git.gnome.org/browse/gedit/commit/?id=41935e289aeb1c9b24372dbe3333e2ba426dd016

I need to do a bit more debugging to see if the bug described here is also fixed.
Comment 2 Sébastien Wilmet 2015-06-07 14:50:14 UTC
Yes, the bug seems to be fixed.
Comment 3 Sébastien Wilmet 2015-06-07 16:19:00 UTC
The bug was fixed with the gedit-metadata-manager, but not with GVFS metadata.

https://git.gnome.org/browse/gedit/commit/?id=f174a0480e6e187437c6df27d457a2740d4abc13

Now it's completely fixed!