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 308324 - "Highlight Misspelled Words" toggle should be retained for new documents
"Highlight Misspelled Words" toggle should be retained for new documents
Status: RESOLVED OBSOLETE
Product: gedit
Classification: Applications
Component: spell checking
3.7.x
Other All
: Normal enhancement
: ---
Assigned To: Gedit maintainers
Gedit maintainers
Depends on:
Blocks:
 
 
Reported: 2005-06-19 19:17 UTC by Thomas M. Hinkle
Modified: 2020-11-24 09:57 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Thomas M. Hinkle 2005-06-19 19:17:55 UTC
Distribution/Version: Ubuntu Hoary

It would be nice if the Auto-Spellcheck toggle was maintained for newly opened
documents.  I realize this isn't *always* what the user wants (I could have a
README in one tab and source code in another), but it is frequently what the
user wants (and especially what a non-expert/non-coding user would want).

For my use case, this is a frequent annoyance, as I have to type Alt-T A for
every document I open to turn autospellcheck on. It's also frustrating since I
unconsciously *assume* spellchecking is turned on for new documents (since I
already turned it on) and then incorrectly assume there are no errors in my
newly opened (but error-filled) document.

In my mind this latter assumption -- presumably shared by many users -- is
reason enough to make the "Autospell-Check" option stick for all newly opened
documents. If the user did not intend for the new document to be spellchecked,
it will be immediately evident what has happened if they open a document and see
 non-words underlined in red. On the other hand, if a user *did* intend for
autospellchecking and opens a new document and spellchecking is turned off,
there is no obvious way for the user to discover that spellchecking is not
happening.

Note, this bug is related to but distint from bug #305055.
Comment 1 Paolo Maggi 2005-07-21 17:35:46 UTC
I agree with you. But I think it should act in a more "sophisticated" way.
If the new file is a file containing code (a C file for example) the 
"Autospell-Check" option should be automatically switched to "off".
Comment 2 Sitsofe Wheeler 2006-03-04 11:23:43 UTC
This looks like a dup of bug #305055
Comment 3 Paolo Maggi 2006-03-04 13:50:12 UTC
As said by the bug reporter this bug is related to but distint from bug #305055.
Comment 4 André Klapper 2012-07-30 15:28:16 UTC
Confirming with 3.2
Comment 5 Ritesh Khadgaray ( irc:ritz) 2013-01-30 11:08:10 UTC
Would be nice, if gedit has an option to leave spell check on by default for new documents ( one where spellcheck metadata is not present ).


__self:

  set metadata::gedit-spell-enabled: 0, to allow gedit to distinguish if spell check was manually disabled, assuming auto-enable spellcheck.
Comment 6 Sébastien Wilmet 2020-11-24 09:57:52 UTC
Mass-closing of all gedit bugzilla tickets.

Special "code" to find again all those gedit bugzilla tickets that were open before the mass-closing:

2bfe1b0590a78457e1f1a6a90fb975f5878cb60064ccfe1d7db76ca0da52f0f3

By searching the above sha256sum in bugzilla, the gedit contributors can find again the tickets. We may be interested to do so when we work on a specific area of the code, to at least know the known problems and possible enhancements.

We do this mass-closing because bugzilla.gnome.org is being replaced by gitlab.gnome.org.