GNOME Bugzilla – Bug 765955
Moving between the search matches sets word_boundaries setting to TRUE
Last modified: 2016-05-04 10:04:46 UTC
In Builder keybinding, when we hit Ctrl+G or Ctrl+Shift+G to move between the search matches, the word_boundaries setting will be set to TRUE. If we are doing a search with word_boundaries being FALSE, hit Ctrl+G, and we are matching entire word only, which is a problem. Moving between the matches should not modify the search settings.
Created attachment 327258 [details] [review] ide-source-view: fix move search
Do you think we should have a tri-state here? (Yes, No, Ingore)
Created attachment 327275 [details] [review] ide-source-view: fix move search I have yet to see a case where we want to explicitly set word_boundaries to FALSE when doing search movements. However, using FALSE for "DO NOTHING" isn't appropriate. In the new patch, I use a gint value for word_boundaries: 0 -> FALSE, 1 -> TRUE, other -> IGNORE. I've added comments for the relevant code in ide_source_view_real_move_search(), to prevent others from trying to "simplify" it.
Review of attachment 327275 [details] [review]: LGTM
Attachment 327275 [details] pushed as 8a94ade - ide-source-view: fix move search