i have unbound F8 however when i press F8 it causes the cursor in the editor window to lose focus and the cursor disappears, ie: something is still happening despite being unbound.
therefore when i subsequently try to use F8 for a custom macro i find the macro still executes but then the focus is lost and i have to click the editor window again. i thought i'd try and "trick" the focus back to the editor window by adding an F2 to the end of the macro but it was to no avail...
after pressing the unbound F8 i can press TAB 7 times and see focus return back to the editor window.
also i've found after pressing the unbound F8 i can press ENTER or SPACE or ESC and focus returns to the editor window.
hth, also btw i tried pressing F8 in other random applications (browsers, other editors, etc.) just to see if i somehow had a global F8 shortcut key defined, but nothing happens when i press F8 elsewhere...
version: geany 1.35 (built on 2019-05-04 with GTK 3.22.30, GLib 2.56.4)
desktop: LXDE
o/s: 5.0.16-100.fc28
--
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/2359
over on geany issues i posted an issue: https://github.com/geany/geany/issues/2359
it seems that when a macro is bound to F8 then the standard GTK event still gets fired after the macro is run.
in the case of F8 it is "give focus to the splitter bar in a paned window" and this event causes the focus on the editor window to be lost, which renders the F8 (or any other combination of a "gtk focus" key) unusable as a macro key.
it appears the standard behaviour in geany for keyboard shortcuts is to *not* fire the GTK event if a shortcut is defined. perhaps the macros plugin should follow the same convention?
a workaround is of course possible: don't use macro keys conflicting with the gtk events: https://developer.gnome.org/hig/stable/keyboard-input.html.en i only discovered geany today and i almost immediately decided to migrate across to it so in the meantime i'll be retraining my brain to not use F8 from my old editor :)
fyi: whilst i was trying to understand the issue i was searching around a bit and found this: https://mail.gnome.org/archives/gtk-app-devel-list/2006-April/msg00338.html an old post which may still be of help.
--
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/issues/928
Hi,
I've been attempting to generate global tags files with the intent of being able to use them with geany to jump to declarations and definitions as necessary, as they would normally be used.
I'm pretty sure I'm doing everything correctly here but I can't seem to get the desired affect.
Here is an example command I used to generate glib tags:
CFLAGS=`pkg-config --cflags glib-2.0` geany -g glib_2_0.c.tags /usr/include/glib-2.0/*.h
it ran without issue. When I try and test it works by jumping to something integral to glib, like "gboolean", it does not work, upon inspection of the generated file it looks like this:
`
g_warn_messageÌ1024Í(const char *domain, const char *file, int line, const char
g_warningÌ131072Í(...)Ö0
g_weak_ref_clearÌ1024Í(GWeakRef *weak_ref)Ö0Ïvoid
g_weak_ref_getÌ1024Í(GWeakRef *weak_ref)Ö0Ïgpointer
g_weak_ref_initÌ1024Í(GWeakRef *weak_ref, gpointer object)Ö0Ïvoid
g_weak_ref_setÌ1024Í(GWeakRef *weak_ref, gpointer object)Ö0Ïvoid
gatomicrefcountÌ4096Ö0Ïvolatile gint
**gbooleanÌ4096Ö0Ïgint**
gcharÌ4096Ö0Ïchar
gchararrayÌ4096Ö0Ïgchar *
gconstpointerÌ4096Ö0Ïconst void *
gdoubleÌ4096Ö0Ïdouble
getÌ1024Í(gpointer cb_data, GSource *source, GSourceFunc *func, gpointer *data)Î
get_propertyÌ1024Í(GObject *object, guint property_id, GValue *value, GParamSpec
getdateÌ1024Í(const char *__string)Ö0Ïtm
getdate_errÌ32768Ö0Ïint
`
I feel like something is going wrong here, looking at a pre-generated tags file there seems to be file paths in each line, presumably to be able to find the file the declaration/definition is in.
Thanks,
Lukas
--
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/2354
Also fixes iterating docs for *Close other Documents* in notebook tab order.
I'd like to add a folder item for *Open in New Window* too.
Screenshot:
You can view, comment on, or merge this pull request online at:
https://github.com/geany/geany/pull/2346
-- Commit Summary --
* Use gtk_widget_show_all in show_tab_bar_popup_menu
* Add *Documents in _Folder* notebook menu
* Remove unnecessary casts
* Iterate in tab order for *Close Other Documents* and close folder items
-- File Changes --
M src/callbacks.c (11)
M src/notebook.c (75)
M src/sidebar.c (1)
-- Patch Links --
https://github.com/geany/geany/pull/2346.patchhttps://github.com/geany/geany/pull/2346.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/pull/2346
I think these are useful to working with xml pair tags.
- Editor Menu option for jumping to matching tag
- Selecting to matching tag
You can view, comment on, or merge this pull request online at:
https://github.com/geany/geany-plugins/pull/763
-- Commit Summary --
* Macro gtk3 compatibility [Needs testing]
* upstream compatibility
* Gtk3 support
* seems I wronged the merge upstream
* Windows installer: update file remove list
* Initialize loop variables to make cppcheck happy
* NEWS: Minor rewording and fix some typos
* Reword item about orphaned plugins
* Unify plugin name spelling
* Set release date for 1.31
* Post release version bump to 1.32
* Keybindings and Editor menu for jump to matching tag and select to matching tag
-- File Changes --
M pairtaghighlighter/src/pair_tag_highlighter.c (86)
-- Patch Links --
https://github.com/geany/geany-plugins/pull/763.patchhttps://github.com/geany/geany-plugins/pull/763.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/763
Depends on #2346, merge that first.
Open all documents matching the document tab's path in a new instance.
I modified two utils.c functions to support this, see commits.
You can view, comment on, or merge this pull request online at:
https://github.com/geany/geany/pull/2352
-- Commit Summary --
* Use gtk_widget_show_all in show_tab_bar_popup_menu
* Add *Documents in _Folder* notebook menu
* Remove unnecessary casts
* Revert whitespace change
* utils_strv_join: Don't free arguments
* utils_start_new_geany_instance: Take a string vector
* notebook menu: Add *Documents in Folder -> Open in New Window* command
-- File Changes --
M src/callbacks.c (3)
M src/highlighting.c (3)
M src/notebook.c (114)
M src/utils.c (15)
M src/utils.h (2)
-- Patch Links --
https://github.com/geany/geany/pull/2352.patchhttps://github.com/geany/geany/pull/2352.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/pull/2352
Using `ctrl+v d` will leave a blank line, cause it inconvenient to paste. It is slightly different from the same operation in vim. Hope it could be the same.
--
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/issues/782
While this might not be necessary technically, cppcheck complained:
overviewscintilla.c:800:53: note: Calling function 'overview_scintilla_get_overlay_color', 2nd argument '&color' value is <Uninit>
overview_scintilla_get_overlay_color (self, &color);
^
overviewscintilla.c:1146:11: note: Uninitialized variable: color
You can view, comment on, or merge this pull request online at:
https://github.com/geany/geany-plugins/pull/916
-- Commit Summary --
* Overview: initialize color variables
-- File Changes --
M overview/overview/overviewscintilla.c (4)
-- Patch Links --
https://github.com/geany/geany-plugins/pull/916.patchhttps://github.com/geany/geany-plugins/pull/916.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/916
Hi,
I use vim quite a lot and noticed a few incorrect behaviours, dw and cw being one.
I'll denote the cursor as a double quote ("), before a letter means it's on that letter.
In geany vimode the following line int the function block:
`void foo(BarClass *pointer) {
std::"cout << pointer->bar_func() << std::endl;
}`
pressing dw or cw would yield:
`void foo(BarClass *pointer) {
std::"pointer->bar_func() << std::endl;
}`
in vim either would yield: (it deletes up to some special characters, not the next word)
`void foo(BarClass *pointer) {
std::"<< pointer->bar_func() << std::endl;
}`
Another example, start again here, with cursor before pointer:
`void foo(BarClass *pointer) {
std::cout << "pointer->bar_func() << std::endl;
}`
geany yields:
`void foo(BarClass *pointer) {
std::cout << "bar_func() << std::endl;
}`
vim yields:
`void foo(BarClass *pointer) {
std::cout << "->bar_func() << std::endl;
}`
Geany vimode also treats dw and cw the same in all cases (apart from dw staying in normal mode and cw entering insert mode, which is correct). In the below example, cursor on B of BarClass:
`void foo("BarClass *pointer) {
std::cout << pointer->bar_func() << std::endl;
}`
for both, geany would yield:
`void foo("pointer) {
std::cout << pointer->bar_func() << std::endl;
}`
dw in vim would yield: (asterisk remains)
`void foo("*pointer) {
std::cout << pointer->bar_func() << std::endl;
}`
cw would yield: (extra space, so when typing new word, space is already there)
`void foo(" *pointer) {
std::cout << pointer->bar_func() << std::endl;
}`
It's worth noting that the special character seem to be specific, so for example underscore is treated as part of the word in vim:
`void foo(BarClass *pointer) {
std::cout << pointer->"bar_func() << std::endl;
}`
dw or cw in vim becomes: (deletes underscore too)
`void foo(BarClass *pointer) {
std::cout << pointer->"() << std::endl;
}`
These seem minor but it is much more often the case that the Alphanum characters and underscore are the ones that the user is considering the 'word' and wants to delete, having to re-type the operators such as '<<' or '-' or '>' etc etc is not the intention.
If it is likely that these changes will get integrated into vimode I would like to offer my services since I work with c and c++ and vim, I think I could get it working just right. Am I ok to dig in?
Thanks,
Lukas
--
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/issues/909
Scintilla does different things when using SCI_WORDRIGHT, SCI_WORDLEFT,
SCI_WORDRIGHTEND and SCI_WORDLEFTEND than what we want for commands like
"w", "b", "W", "B", "e", "E", etc. For instance, for
ident1 = id|ent2+ident3;
where | represents the cursor, SCI_WORDRIGHT does
ident1 = ident2+|ident3;
while Vim's "w" does
ident1 = ident2|+ident3;
For this reason we have to reimplement all the word navigation by ourselves
to better emulate the behavior of Vim. This patch tries to do that.
Should fix #909
You can view, comment on, or merge this pull request online at:
https://github.com/geany/geany-plugins/pull/919
-- Commit Summary --
* vimode: Don't use word navigation from Scintilla
-- File Changes --
M vimode/src/cmds/motion.c (288)
-- Patch Links --
https://github.com/geany/geany-plugins/pull/919.patchhttps://github.com/geany/geany-plugins/pull/919.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/919