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 659871 - API to override/customize spell check
API to override/customize spell check
Status: RESOLVED DUPLICATE of bug 719978
Product: gtksourceview
Classification: Platform
Component: Syntax files
unspecified
Other Linux
: Normal normal
: ---
Assigned To: GTK Sourceview maintainers
GTK Sourceview maintainers
Depends on:
Blocks:
 
 
Reported: 2011-09-22 20:15 UTC by John Stowers
Modified: 2014-02-08 23:04 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description John Stowers 2011-09-22 20:15:39 UTC 
For the latex plugin it would be helpful if there was some way to tell the spell checking plugin to ignore all LaTeX syntax, things inside commands (like \label{foo-bar}), etc.

The old latex spelling plugin used to do this.
Comment 1 Ignacio Casal Quinteiro (nacho) 2011-09-22 20:17:30 UTC 
you can do this by modifying the latex.lang file. Just provide a patch for it.
Comment 2 John Stowers 2011-09-22 20:23:22 UTC 
That will only get us halfway - what about when one redefines commands, etc?
Comment 3 Ignacio Casal Quinteiro (nacho) 2011-09-22 20:25:37 UTC 
can't you provide a regex for that? we provide a regex that matches all this stuff and we mark it to not get it highlighted
Comment 4 John Stowers 2011-09-22 20:34:50 UTC 
I dont think a static regex that lives in the latex.lang file is enough here; consider

\newcommand{\jrefSec}[1]{Section \ref{#1}}

I think it would need to be dynamic, once the language model is built to ignore \jrefSec{sec:foo-bar}
Comment 5 Ignacio Casal Quinteiro (nacho) 2011-09-22 20:58:48 UTC 
mmm, yeah you are right, although I think we should focus first in other stuff like the completion or snippets etc as this is not that bad.
Comment 6 Sébastien Wilmet 2014-02-08 23:04:56 UTC 

*** This bug has been marked as a duplicate of bug 719978 ***