I’ve been using Geany with patches whereby [typeahead search](https://developer.gnome.org/gtk3/stable/GtkTreeView.html#gtk-tree-v… in the symbols list and in [TreeBrowser](http://plugins.geany.org/treebrowser.html) uses [`g_str_match_string`](https://developer.gnome.org/glib/stable/glib-String-Utility-Functions.html#g-str-match-string) instead of simply matching by prefix.
Now, when I type “ba”, it finds not just `bar` but also `foo_bar` and `foo-bar`, etc. (not `FooBar` though).
It’s convenient.
The change itself is simple (all the heavy lifting is in GTK+/GLib), but I’m pretty sure this behavior cannot be made the default, as it might cause too many false positives, and would break habits.
What do you think of having such a feature as an option?
If suitable, what do you think its granularity should be? Should it be a checkbox for every tree view where it makes sense, like “Use fuzzy search in symbols list”, “Use fuzzy search in documents list” and so on?
(Also, I’m not sure it should be just [`g_str_match_string`](https://developer.gnome.org/glib/stable/glib-String-Utility-Functions.html#g-str-match-string). Maybe typing “ba” should find `FooBar` as well. Maybe typing “fb” should find `foo_bar`, like in [Commander](http://plugins.geany.org/commander.html).)
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/issues/1466
This pull request consists of 2 patches:
1. It remembers selection in the sidebar and on project reload the selected row is restored.
2. It stores/loads expanded paths to/from the project file so the state of the tree gets restored when switching between projects.
You can view, comment on, or merge this pull request online at:
https://github.com/geany/geany-plugins/pull/1144
-- Commit Summary --
* projectorganizer: Remember selected row in sidebar when reloading
* projectorganizer: Store/load expanded paths in the sidebar to project file
-- File Changes --
M projectorganizer/src/prjorg-main.c (5)
M projectorganizer/src/prjorg-project.c (25)
M projectorganizer/src/prjorg-project.h (1)
M projectorganizer/src/prjorg-sidebar.c (48)
M projectorganizer/src/prjorg-sidebar.h (2)
-- Patch Links --
https://github.com/geany/geany-plugins/pull/1144.patchhttps://github.com/geany/geany-plugins/pull/1144.diff
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany-plugins/pull/1144
It seems that GDK_MOD2_MASK isn't the right modifier to check for
command pressed - its mapping is platform-specific and while this works
on macOS, it has undesirable side-effects on linux. Use GDK_META_MASK
instead which based on my testing seems to do the right thing both on
macOS and linux.
Fixes (1) in #1136
You can view, comment on, or merge this pull request online at:
https://github.com/geany/geany-plugins/pull/1141
-- Commit Summary --
* vimode: fix escape not working when numlock is on
-- File Changes --
M vimode/src/keypress.c (2)
-- Patch Links --
https://github.com/geany/geany-plugins/pull/1141.patchhttps://github.com/geany/geany-plugins/pull/1141.diff
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany-plugins/pull/1141
I'm surprised there isn't already an issue for this, but I can't find it, better googlers may.
The python checks and commands used in the build need updating to python3. The `python` command does not exist on many systems now.
1. `configure.ac` checks for `python` so the docs have to be disabled here, even though I have `python3` and a `rst2html` with `#!/usr/bin/python3` shebang.
2. `geany_gtkdoc_header.m4` explicitly checks for Python 2.7 if I read it right.
3. ctags tests all the .py files use `#!/usr/bin/python` or `#!/usr/bin/env python` both of which will fail
4. as above for scripts
5. python templates use `#!/usr/bin/env python`
There may be more.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/issues/2896