Geany currently loads only plugins with the ".so" extension on macOS. This extension is still needed since we use autotools for geany-plugins which also generate ".so".
I tested it and it does nothing on linux while on macOS it changes the extension correctly to ".so".
Unless it's a big a problem, I'd like to have this merged for 2.0 so I can use meson for the build.
Fixes #3606.
You can view, comment on, or merge this pull request online at:
https://github.com/geany/geany/pull/3608
-- Commit Summary --
* mscos: use ".so" extension for plugins instead of ".dylib"
-- File Changes --
M plugins/meson.build (6)
-- Patch Links --
https://github.com/geany/geany/pull/3608.patchhttps://github.com/geany/geany/pull/3608.diff
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/pull/3608
You are receiving this because you are subscribed to this thread.
Message ID: <geany/geany/pull/3608(a)github.com>
Update the GPL note template with the latest version found on gnu.org. It includes the transition from GPLv2 to GPLv3, and refers to a website instead of a postal address for the text of the GNU GPL.
You can view, comment on, or merge this pull request online at:
https://github.com/geany/geany/pull/3549
-- Commit Summary --
* Update GPL note template
-- File Changes --
M data/templates/gpl (11)
-- Patch Links --
https://github.com/geany/geany/pull/3549.patchhttps://github.com/geany/geany/pull/3549.diff
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/pull/3549
You are receiving this because you are subscribed to this thread.
Message ID: <geany/geany/pull/3549(a)github.com>
The condition is wrong and for version 2.0 it will constantly report there's an update available when upgrading from 1.x (where x > 0).
I had a "visionary" moment regarding possible 2.0 problems and had a look at the updatechecker plugin if it handles major versions - id does, but wrongly (in addition, there are two identical conditions for the "minor" version but the "mini" version check is missing).
I haven't tested this at all (not sure how to test when there's no actual release).
@b4n @eht16 I think this or some other variant of this patch should go to 2.0.
You can view, comment on, or merge this pull request online at:
https://github.com/geany/geany-plugins/pull/1284
-- Commit Summary --
* updatechecker: Fix logic comparing version numbers
-- File Changes --
M updatechecker/src/updatechecker.c (22)
-- Patch Links --
https://github.com/geany/geany-plugins/pull/1284.patchhttps://github.com/geany/geany-plugins/pull/1284.diff
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany-plugins/pull/1284
You are receiving this because you are subscribed to this thread.
Message ID: <geany/geany-plugins/pull/1284(a)github.com>
Fixed deprecated gtk3 calls. The PR unfortunately includes an ugly list of all the GTK stockitems as I did not see a different solution.
You can view, comment on, or merge this pull request online at:
https://github.com/geany/geany-plugins/pull/865
-- Commit Summary --
* commander: fixed deprecated gtk3 calls
-- File Changes --
M build/commander.m4 (1)
M commander/src/Makefile.am (7)
M commander/src/commander-plugin.c (22)
M utils/src/Makefile.am (3)
A utils/src/gp_gtkcompat.c (222)
M utils/src/gp_gtkcompat.h (5)
-- Patch Links --
https://github.com/geany/geany-plugins/pull/865.patchhttps://github.com/geany/geany-plugins/pull/865.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/865
Geany's markdown syntax highlighting (without the markdown plugin) is confused, when image link without title is used:
```
```
All the following text is highlighted bold (same as the link itself).
Also the following markdown syntax is ignored - see ```*Obecné*``` is not in italics.
When I fill in some title to image link
```
```
then the highlighting became correct (i.e. only link itself is bold).
Also the following markdown syntax is ok then (*```*Obecné*```* **is** in italics).
The correct behavior is to highlight bold only the link even if its title is empty.
--
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/2798
I'm using the geany 1.32 default installation on ubuntu 18.04 64bit to edit test.md file.
for H1 - H6 headers, the "#" signs are bold, but not the rest of header, i.e. "# Header" only has bold for '#' not for the word 'Header'.
`**bold**` does not show bold, neither does `*italiic*` displays italic.
I can customize them all using filetypes.markdown, except for the H1-H6 headers, the header is not impacted at all as mentioned above, for example:
`header1=0xFFCB4F;0x1E1E1E;true;false` this change will make `#` bold with specified background/front color, but not the header content, i.e. "Header1" in `# Header1` stays non-bold.
At least I would like to have all markdown headers shown as bold inside Geany without the need of any previewer
--
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/2026
I'm not sure how robust our parser is against invalid input or updated ctags file format so better use the upstream version of the official library to parse ctags files so we don't have to worry about this.
In addition, this patch also updates the code to read all the ctags kinds we need in tagmanager.
You can view, comment on, or merge this pull request online at:
https://github.com/geany/geany/pull/3049
-- Commit Summary --
* Add ctags 'readtags' library to allow us parse ctags files
* Use the readtags library to parse ctags files
-- File Changes --
M ctags/Makefile.am (2)
A ctags/libreadtags/readtags.c (1310)
A ctags/libreadtags/readtags.h (295)
M src/tagmanager/Makefile.am (1)
M src/tagmanager/tm_source_file.c (174)
-- Patch Links --
https://github.com/geany/geany/pull/3049.patchhttps://github.com/geany/geany/pull/3049.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/3049
188038a06a1050308fd7621f11147883d7e5b8fc extended the formatting options, but a blooper made it effectively ignore the language-specific rules, always using the default one. This affects formatting for Go, Pascal and Python, as well as introducing memory leaks for those.
You can view, comment on, or merge this pull request online at:
https://github.com/geany/geany/pull/3604
-- Commit Summary --
* Fix blooper leading to incorrect variable formatting
-- File Changes --
M src/tagmanager/tm_parser.c (3)
-- Patch Links --
https://github.com/geany/geany/pull/3604.patchhttps://github.com/geany/geany/pull/3604.diff
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/pull/3604
You are receiving this because you are subscribed to this thread.
Message ID: <geany/geany/pull/3604(a)github.com>