Passing filenames *does not* disable loading session.
Mention *Open new files from the command-line* pref.
Remove redundant note about line number and column number.
You can view, comment on, or merge this pull request online at:
https://github.com/geany/geany/pull/3405
-- Commit Summary --
* Update CLI filenames docs
-- File Changes --
M doc/geany.txt (28)
-- Patch Links --
https://github.com/geany/geany/pull/3405.patchhttps://github.com/geany/geany/pull/3405.diff
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/pull/3405
You are receiving this because you are subscribed to this thread.
Message ID: <geany/geany/pull/3405(a)github.com>
On linux, wayland (without xwayland), be it with weston or sway,
ctrl + mouse wheel will not zoom / zoom out
shift + mouse wheel will not scroll horizontally.
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/issues/3226
You are receiving this because you are subscribed to this thread.
Message ID: <geany/geany/issues/3226(a)github.com>
If geany has a clean shutdown using Quit from the file menu, it remembers which documents are open, and reloads them when it is next restarted. This doesn't happen in the case of a forced quit, such as my computer freezing and needing a reboot (which unfortunately happens fairly frequently for me). Is there any way to force the config file to be updated periodically to record the currently opened documents?
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/issues/3324
You are receiving this because you are subscribed to this thread.
Message ID: <geany/geany/issues/3324(a)github.com>
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
Geany is my favorite IDE, but sometimes I use VSCode in certain instances. One feature that I really wish was in Geany is the "Gutter Indicators" that show when a line is modified, deleted, or added.
Here is an example from VS Code
This might be possible using the Scintilla margin API and [libgit2](https://libgit2.org/)
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany-plugins/issues/1244
You are receiving this because you are subscribed to this thread.
Message ID: <geany/geany-plugins/issues/1244(a)github.com>