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 566982 - don't autocomplete inside string or comment
don't autocomplete inside string or comment
Product: anjuta
Classification: Applications
Component: plugins: language-support-c-cpp-java
Other Linux
: Normal normal
: ---
Assigned To: Naba Kumar
Anjuta maintainers
Depends on: 472660
Reported: 2009-01-08 05:08 UTC by Adam Dingle
Modified: 2010-01-10 13:47 UTC
See Also:
GNOME target: ---
GNOME version: ---

screenshot (92.78 KB, image/png)
2009-01-08 05:11 UTC, Adam Dingle

Description Adam Dingle 2009-01-08 05:08:22 UTC
Anjuta offers symbol autocompletions even when I'm typing a string constant or comment.  This is annoying, since most words in these contexts are not symbols.  We shouldn't offer autocompletions in these contexts.
Comment 1 Adam Dingle 2009-01-08 05:11:47 UTC
Created attachment 125999 [details]
Comment 2 Massimo Cora' 2009-01-08 08:36:00 UTC
this is language-support related.
Comment 3 Johannes Schmid 2009-01-08 09:57:59 UTC
I think scintilla doesn't autocomplete inside a comment or string. Unfortunately, gtksourceview does not export this information. There is a bug in gtksourceview about it, though I don't have the number handy currently.

Can you check if this also happens with scintilla? Otherwise, I will reassign it to gtksourceview.
Comment 4 Massimo Cora' 2009-01-08 12:48:25 UTC
Scintilla autocompletes if you explicit tell it to do so.
in the example it'll autocomplete only if you open the braket "main ("
Comment 5 Adam Dingle 2009-01-08 14:28:29 UTC
I just tried this in Scintilla.  The behavior is exactly the same as in gtksourceview: Anjuta offers autocompletions even when I'm typing a comment or string constant.
Comment 6 Johannes Schmid 2010-01-10 13:47:24 UTC
This problem has been fixed in the development version. The fix will be available in the next major software release. Thank you for your bug report.