Vesion: Geany 1.37.1
OS: Arch Linux
Graphical Environment: Sway (Wayland) but also occurs on other Wayland compositors
Whenever Geany is on my second monitor, the pop up autocomplete dialog is invisible. It still exists as pressing enter selects an entry but it is simply not rendered. Behavior on my primary monitor is normal and the menu renders. I spent some time looking into whether or not this was specific to Wayland or GTK and found several reported issues for other programs that seemed relevant.
According to [this comment](https://github.com/swaywm/sway/issues/3135#issuecomment-448794177) issues with incorrect positioning of popups is related to the use of `gtk_menu_popup ()` which was deprecated in GTK 3.22. Replacing it with something like `gtk_menu_popup_at_widget()` or another appropriate function may fix my issue. Apologies for not submitting a PR but I'm not well-versed in C nor GTK.
--
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/2820
Fix #864
Note that I didn't workout regex since it seems to break group number conventions.
Also for this to work we must reset LANG envvar (maybe provide an option?) since gcc translates words "error", "warning", "note".
You can view, comment on, or merge this pull request online at:
https://github.com/geany/geany/pull/1649
-- Commit Summary --
* warning support
-- File Changes --
M data/filedefs/filetypes.common (1)
M src/build.c (14)
M src/build.h (2)
M src/editor.h (3)
M src/filetypes.c (3)
M src/filetypes.h (11)
M src/highlighting.c (7)
M src/msgwindow.c (48)
M src/msgwindow.h (6)
-- Patch Links --
https://github.com/geany/geany/pull/1649.patchhttps://github.com/geany/geany/pull/1649.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/1649
On OSX (since a long time), scroll quickly in any direction using the wheel, then click in the window. Do it repeatedly. You will find that there is a high chance that some variable indicating the current state of the scrollbar and scrollable area is actually farther than was shown, as clicking in the window suddenly makes the whole screen jump to the new position, which may be only a few lines further than was shown, or more than a screenful, depends. It is not normal that the document be scrolled by just clicking in it (except at the very bottom if the last line is partially displayed, and then that special case only scrolls up by one line).
Sometimes while using the wheel, the scrollable area shows two different portions of the document in a kind of accidental split screen, but I can't tell whether this is a separate bug or the same bug.
This is a 3rd-party mouse with a traditional stepping wheel. I don't have a touch sensor mouse to compare with. But now I just tried with the laptop's trackpad and the same happens as with the mouse wheel, using regular two-finger drag. When using a fling gesture, however, after the first redraw of the screen, there's a pause until about 3/4 of a second after touch-up (the equivalent of button release), before suddenly a long series of screen updates happens, whereas normally screen updates should be equally-spaced during the gesture and the decelerating motion that continues for a while.
Compare what those 3 cases (wheel, 2-finger drag, 2-finger fling) do in other apps (e.g. I tried with Firefox OSX using a long enough web page.)
--
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-osx/issues/19
I'm using the 1.38.0-3 build and it appears, that after I've typed something inside editor widget, the mousewheel (classic 3 buttons wheel mouse via USB) is not working. It recovers, when switching windows and coming back to Geany.
--
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-osx/issues/34
On Linux, after copying a rectangular selection into the clipboard, it is possible to paste it into existing text while maintaining the rectangular structure (and not insert newlines where none existed before). On a Mac, this appears to be broken.
Geany 1.37
Using GTK+ v3.24.20 and GLib v2.66.0 runtime libraries
System Version: macOS 10.15.7 (19H15)
Kernel Version: Darwin 19.6.0
Example. I want to move the two lines of "hub." into the links above:
But when I do a rectangular select (using the mouse since the keys don't work.......that's a different issue), the result of pasting does not at all look like it would on Linux. It looks like this:
When it should look like this:
--
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/2685
I cannot see emoji characters in the editor. The emoji keyboard shortcut (Ctrl + Cmd + Spacebar) also does not work within this app. They can be pasted, and successfully copied back out, but they are invisible.
On macOS Big Sur 11.5.1, Intel chip.
--
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-osx/issues/27
Hi.
OS: Windows 7 64bits
Geany version: 1.26
In "Edit>Preferences>Files>Default encoding" I selected IBM850 as default encoding in all options, new files and open files, but all files are opened with 1252 encoding. With new files there is no problem.
Thank you.
---
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/issues/900
... that way new users don't have to be told to uncomment the heading as well as the setting they need, just the setting line.
And document this commenting behaviour in the manual.
--
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/2689
- By the original design, the debugger allows thread context switching only
interactively, while in the Call Stack pane (in Stopped mode). This is
being handled directly through GtkTreeView::cursor-changed event.
- However, this event was also getting triggered when clearing the latest
thread's Call Stack after continuing the execution (Running mode).
- This behavior does not seem to have being intended, and it lead to a
number of issues: stepping hangs, corruption of GDB output processing,
unnecessary attempts at opening of source files corresponding to thread's
call-stack frames.
- To avoid all of these issues, GtkTreeView::cursor-changed event is left
unhandled while clearing the frames. Also the handler for thread-context
switching is allowed processing only in debugger's Stopped mode to enforce
the intended behavior.
Fixes #1069
You can view, comment on, or merge this pull request online at:
https://github.com/geany/geany-plugins/pull/1170
-- Commit Summary --
* Debugger: Fix debugging of multi-threaded programs
-- File Changes --
M debugger/src/debug.c (4)
M debugger/src/stree.c (14)
-- Patch Links --
https://github.com/geany/geany-plugins/pull/1170.patchhttps://github.com/geany/geany-plugins/pull/1170.diff
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany-plugins/pull/1170
You are receiving this because you are subscribed to this thread.
Message ID: <geany/geany-plugins/pull/1170(a)github.com>