Hi,
I have experienced troubles with popups in last version of Geany on Wayland. The context menu never shows and this message is printed to stdout:
```
Gdk-Message: 07:03:47.840: Window 0x55a9f5030360 is a temporary window without parent, application will not be able to position it on screen.
(geany:1327711): Gdk-CRITICAL **: 07:03:47.846: gdk_wayland_window_handle_configure_popup: assertion 'impl->transient_for' failed
```
Also, the code-completion popups never show. Interestingly, when trying to invoke code-completion, no error is logged. So it might or might not be a different issue.
**Steps to reproduce:**
1. Open Geany on wayland (I'm using sway on Arch Linux, not sure if it works in other WMs/distros)
2. Right click in the editor
3. Nothing happens. No context menu is shown, only message appears on the stdout...
**Versions**
```
$ geany --version
geany 1.38 (built on 2021-10-09 with GTK 3.24.30, GLib 2.70.0)
```
```
$ pacman -Q geany gtk3 wayland wayland-protocols
geany 1.38-1
gtk3 1:3.24.30+90+g20be04f7ac-1
wayland 1.19.0-2
wayland-protocols 1.23-1
```
**Additional info**
I have tested the same with SciTE (Version 5.1.5 Scintilla:5.1.4 Lexilla:5.1.3 compiled for GTK:3.24.30) and it shows context menu just fine, so it is probably not Scintilla bug.
I have also tried with current master (5d4e7cfd5b12647b4cab9bda7278abd7f63e9c2f) in hope that #2930 might have fixed it. Unfortunately, it behaves just the same, no popups, just shows error.
--
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/3009
## Abstract
You can't replace the license templates such as "gpl" with your own ones.
## Steps to reproduce
1. `echo "test template" > ~/.config/geany/templates/test`
1. `sed -i 's/{gpl}/{test}/' ~/.config/geany/templates/fileheader`
1. (Re-)open Geany
1. File → New (with template) → main.c
## Expected behavior
```
/*
* ...
* test template
*/
```
## Actual behavior
```
/*
* ...
* {test}
*/
```
--
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/1391
#1017 continuation, new (last) attempt.
You can view, comment on, or merge this pull request online at:
https://github.com/geany/geany/pull/1752
-- Commit Summary --
* Add AutoIt syntax highlighting and Ctags parser for AutoIt
-- File Changes --
M ctags/Makefile.am (1)
M ctags/main/parsers.h (3)
A ctags/parsers/autoit.c (121)
M data/Makefile.am (3)
A data/filedefs/filetypes.autoit (72)
M data/filetype_extensions.conf (1)
M scintilla/Makefile.am (1)
A scintilla/lexers/LexAU3.cxx (910)
M scintilla/scintilla_changes.patch (2)
M scintilla/src/Catalogue.cxx (1)
M src/filetypes.c (1)
M src/filetypes.h (1)
M src/highlighting.c (9)
M src/highlightingmappings.h (35)
M src/symbols.c (8)
M src/tagmanager/tm_parser.c (5)
M src/tagmanager/tm_parser.h (1)
M tests/ctags/Makefile.am (1)
A tests/ctags/simple.au3 (32)
A tests/ctags/simple.au3.tags (5)
-- Patch Links --
https://github.com/geany/geany/pull/1752.patchhttps://github.com/geany/geany/pull/1752.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/1752
It would be nice to have a feature to collapse all tags of xml text (or other code) to, say level 1 or level 2.
--
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/3041
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