The NumberedBookmarks plugin saves the bookmarks. If Geany is terminated and the file modified, and later again opened by Geany, the plugin issues a warning for every open file, that the bookmarks can't be restored.
This is annoying, when working - for instance - with Git. When I terminate Geany, checkout a different branch, and restart Geany, the files will be reloaded, but of course based on the version of the new branch. This will invalidate the bookmarks of all files. This can't be helped, but in this case, I don't want to manually acknowledge the bookmark warning for every file. I would prefer instead that the bookmarks silently are reset, if it is not possible to restore them.
Since not everyone will probably want this behaviour, this should be configurable.
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany-plugins/issues/1367
You are receiving this because you are subscribed to this thread.
Message ID: <geany/geany-plugins/issues/1367(a)github.com>
Currently, the plugin remembers bookmarks only when I save the file.
If I just look at a file and set bookmarks for the purpose of analysis, and then quit Geany (since nothing in the file is changed, I can't force Geany to "save" the file), the bookmarks are lost.
It would be great, if bookmark remembering would not only happen on saving, but also on quitting.
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany-plugins/issues/1366
You are receiving this because you are subscribed to this thread.
Message ID: <geany/geany-plugins/issues/1366(a)github.com>
This patch:
- adds a scripts/update-themes.py script copying themes with compatible licenses (themes with no explicit license are skipped for now)
- copies these themes under data/colorschemes
- adds lgpl-2.0.txt, lgpl-2.1.txt, gpl-3.0.txt to data/colorschemes to cover themes not falling under Geany'sGPL 2.0 or later
Fixes #4035.
You can view, comment on, or merge this pull request online at:
https://github.com/geany/geany/pull/4044
-- Commit Summary --
* Add themes from geany-themes
-- File Changes --
M data/Makefile.am (43)
A data/colorschemes/abc-dark.conf (120)
A data/colorschemes/abc-light.conf (120)
A data/colorschemes/bespin.conf (121)
A data/colorschemes/black.conf (125)
A data/colorschemes/cyber-sugar.conf (135)
A data/colorschemes/darcula.conf (149)
A data/colorschemes/dark-colors.conf (136)
A data/colorschemes/dark-fruit-salad.conf (121)
A data/colorschemes/dark.conf (120)
A data/colorschemes/delt-dark.conf (106)
A data/colorschemes/earthsong.conf (120)
A data/colorschemes/epsilon.conf (117)
A data/colorschemes/evg-ega-dark.conf (148)
A data/colorschemes/gedit.conf (120)
A data/colorschemes/github.conf (122)
A data/colorschemes/gpl-3.0.txt (674)
A data/colorschemes/grey8.conf (116)
A data/colorschemes/hacker.conf (116)
A data/colorschemes/himbeere.conf (135)
A data/colorschemes/inkpot.conf (118)
A data/colorschemes/kugel.conf (132)
A data/colorschemes/lgpl-2.0.txt (480)
A data/colorschemes/lgpl-2.1.txt (501)
A data/colorschemes/matcha.conf (130)
A data/colorschemes/mc.conf (117)
A data/colorschemes/metallic-bottle.conf (115)
A data/colorschemes/notepad-plus-plus.conf (122)
A data/colorschemes/oblivion2.conf (120)
A data/colorschemes/one-dark.conf (148)
A data/colorschemes/pygments.conf (131)
A data/colorschemes/retro.conf (115)
A data/colorschemes/sleepy-pastel.conf (102)
A data/colorschemes/slushpoppies.conf (120)
A data/colorschemes/solarized-dark.conf (147)
A data/colorschemes/solarized-light.conf (147)
A data/colorschemes/spyder-dark.conf (118)
A data/colorschemes/steampunk.conf (123)
A data/colorschemes/tango-light.conf (120)
A data/colorschemes/tinge.conf (128)
A data/colorschemes/ubuntu.conf (116)
A data/colorschemes/vibrant-ink.conf (123)
A scripts/update-themes.py (106)
-- Patch Links --
https://github.com/geany/geany/pull/4044.patchhttps://github.com/geany/geany/pull/4044.diff
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/pull/4044
You are receiving this because you are subscribed to this thread.
Message ID: <geany/geany/pull/4044(a)github.com>
I'm using geany 2.0-1 on Arch Linux with XFCE.
Since the newest update, I can not use paste via middle-click repeatedly anymore. This was a frequent use case for me: select some text and then paste it at a few places. It does not matter if the selection was made inside or outside geany.
What makes me think geany clears the X selection:
* I can select and paste into a different window multiple times, but after pasting into geany, I can't anymore.
* Also, the clipboard manager plugin for the XFCE panel shows no mouse selection anymore afterwards.
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/issues/3658
You are receiving this because you are subscribed to this thread.
Message ID: <geany/geany/issues/3658(a)github.com>
`if [[ $(type -t "editions_${OS}") == function ]]; then`
showing this line as function in symbols, even it isn't really function.
Wasn't like that in older version
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/issues/3661
You are receiving this because you are subscribed to this thread.
Message ID: <geany/geany/issues/3661(a)github.com>
Standard gettext should be used over glib's glue these days.
AM_GLIB_GNU_GETTEXT and glib-gettextize are deprecated. This helps
possible meson build (no concrete plans yet) as well as working with
intltool is harder over there. gettext, on the other hand, is supported
out of the box in meson.
Beware, autopoint is a new dependency when building from git,
should not affect tarballs. Also, it's already required by Geany core.
Additionally, autogen.sh follows Geany's autogen.sh more closely,
allowing for out-of-tree builds.
You can view, comment on, or merge this pull request online at:
https://github.com/geany/geany-plugins/pull/1183
-- Commit Summary --
* Use standard gettext, following Geany core.
* Fix issues found by standard gettext
* Update po files after gettext transition.
-- File Changes --
M .github/workflows/build.yml (1)
M .gitignore (7)
M autogen.sh (11)
M build/common.m4 (1)
M build/i18n.m4 (10)
M configure.ac (8)
A po/LINGUAS (1)
A po/Makevars (82)
M po/POTFILES.in (8)
M po/be.po (710)
M po/ca.po (771)
M po/da.po (697)
M po/de.po (966)
M po/el.po (690)
M po/es.po (952)
M po/fr.po (950)
M po/gl.po (780)
M po/it.po (847)
M po/ja.po (770)
M po/kk.po (720)
M po/nl.po (812)
M po/pt.po (0)
M po/pt_BR.po (0)
M po/ru.po (0)
M po/tr.po (0)
M po/uk.po (0)
M po/zh_CN.po (0)
M treebrowser/src/treebrowser.c (0)
-- Patch Links --
https://github.com/geany/geany-plugins/pull/1183.patchhttps://github.com/geany/geany-plugins/pull/1183.diff
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany-plugins/pull/1183
You are receiving this because you are subscribed to this thread.
Message ID: <geany/geany-plugins/pull/1183(a)github.com>
The symbol tree construction code assumes that tag parents appear before their children. At the moment tag list is sorted by line numbers which works for C structs
```C
struct Foo {
int bar;
int baz;
}
```
where the tag Foo (which is a parent of bar and baz) is sorted before bar and baz. However, this doesn't work when the name of the struct (or a variable of an anonymous struct) follows the struct members such as in the following SystemVerilog example:
```systemverilog
struct packed {
byte s_a, s_b, s_c;
string s_str;
} s_member;
```
Here the members are sorted before the parent and the symbol tree construction code doesn't work correctly.
This patch sorts symbols so that parents are sorted before their members - only if tags aren't in a parent-child relationship the original sorting by line is performed.
@b4n Does this look alright to you?
Fixes #4060.
You can view, comment on, or merge this pull request online at:
https://github.com/geany/geany/pull/4063
-- Commit Summary --
* Make sure that parents appear before their children when constructing symbol tree
-- File Changes --
M src/symbols.c (40)
-- Patch Links --
https://github.com/geany/geany/pull/4063.patchhttps://github.com/geany/geany/pull/4063.diff
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/pull/4063
You are receiving this because you are subscribed to this thread.
Message ID: <geany/geany/pull/4063(a)github.com>
When the user drags the message window or the sidebar window too much towards the edge of the main window, it may become too hard or even impossible to drag them back as towards the edge of the main window the cursor resizes the main window and doesn't allow dragging the sidebar separator. The only workaround in this case is to manually edit the Geany config file which is annoying.
This patch does two things:
1. When the sidebar/msgwindow divider is dragged to the edge of the window, at the 10px distance from the window border it "snaps" completely to the edge and toggles sidebar/msgwindow visibility.
2. When sidebar/msgwindow is toggled to be shown again, if its previous distance from the edge of the window is less than 10px, its size is restored to some reasonable size (300px for the sidebar, 200px for the message window)
This patch has been tested with all the sidebar/msgwindow location settings and should work correctly in all the configurations.
Fixes #4017.
Fixes #1753.
Fixes #3329.
You can view, comment on, or merge this pull request online at:
https://github.com/geany/geany/pull/4023
-- Commit Summary --
* Improve sidebar and message window resizing behavior
-- File Changes --
M data/geany.glade (2)
M src/callbacks.c (37)
M src/msgwindow.c (15)
M src/ui_utils.c (13)
-- Patch Links --
https://github.com/geany/geany/pull/4023.patchhttps://github.com/geany/geany/pull/4023.diff
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/pull/4023
You are receiving this because you are subscribed to this thread.
Message ID: <geany/geany/pull/4023(a)github.com>
In https://github.com/geany/geany/pull/4013 I forgot to add a unit test for meson.
However, when I tried to add it now (naming the test file `meson.build`), I got the following in `meson.build.log`:
```
Unknown filetype extension for "/tmp/tmp.XJrc9S8Suo/test.build.tags".
```
The reason is that unlike other filetypes, the Meson configuration in `filetype_extensions.conf` doesn't start with `*.` but instead the whole filename is used:
```
Meson=meson.build;meson.options;meson_options.txt;
```
The unit test runner creates test files starting with `test`, followed by the filetype extension and this doesn't match what's in `filetype_extensions.conf`.
What should we do about it?
A simple (but ugly) way would be to add some `*.meson_unittest` extension to `filetype_extensions.conf` which we would use for the unit test but which wouldn't be used in real life.
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/issues/4074
You are receiving this because you are subscribed to this thread.
Message ID: <geany/geany/issues/4074(a)github.com>
Hey guys, for those who using Geany on Windows OS and want a dark theme ui like monokai theme, you can just clone my repo [Geany-WebDev-Snippets](https://github.com/zhaolinlau/Geany-WebDev-Snippets) and go to `Geany-WebDev-Snippets -> themes -> monokai`, then drag the whole `gtk-3.0` folder to your `C:\Users\Win10\AppData\Local`.
After that, your Geany will be transform from this
to this
And I will add more themes to my repo in the future.
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/discussions/3283
You are receiving this because you are subscribed to this thread.
Message ID: <geany/geany/repo-discussions/3283(a)github.com>