With only few lines of code modification, I am now using the Mardown geany plugin as a svg image viewer (adding any other file that a Webkit supports is possible too, I only added .svg and .html). This is really handy for me; I can now write my code, run them and plot the outpouts without leaving geany IDE :-). Any interest in merging these with the upsteram branch?
A side note: I have also changed the (internal) name of Tree Browser, the previous one kept appearing after Scope plugin tabs which was not ideal
You can view, comment on, or merge this pull request online at:
https://github.com/geany/geany-plugins/pull/822
-- Commit Summary --
* markdown plugin extended: now it supports viewing .svg and .html files
* Update viewer.c
* Update README
-- File Changes --
M markdown/README (3)
M markdown/src/plugin.c (18)
M markdown/src/viewer.c (9)
M treebrowser/src/treebrowser.c (2)
-- Patch Links --
https://github.com/geany/geany-plugins/pull/822.patchhttps://github.com/geany/geany-plugins/pull/822.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/822
I have filed a feature request for scintilla for the above, it would be great to have commonmark markdown syntax supported in this plugin as well since current markdown support is limited to basic markdown.
--
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/issues/651
Hello, Everyone!
It would be great to have the [CommonMark](http://commonmark.org/) plugin.
The rationale:
> We propose a standard, unambiguous syntax specification for Markdown, along with a suite of comprehensive tests to validate Markdown implementations against this specification. We believe this is necessary, even essential, for the future of Markdown.
>
> That’s what we call CommonMark.
>
> — [CommonMark](http://commonmark.org/).
Best regards,
Sergey Brunov.
--
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/issues/589
There is more choice when using icons based on freedesktop icon name
so we can use better icons.
This is mainly because of "New file" and "New directory" icons in the popup menu in the sidebar which should use action icons instead of icons of a file and a directory (with some themes all action icons are black and white while document/directory icons have a color which looks inappropriate in this case).
You can view, comment on, or merge this pull request online at:
https://github.com/geany/geany-plugins/pull/932
-- Commit Summary --
* projectorganizer: don't use stock icons
-- File Changes --
M projectorganizer/src/prjorg-menu.c (18)
M projectorganizer/src/prjorg-sidebar.c (59)
M projectorganizer/src/prjorg-utils.c (15)
M projectorganizer/src/prjorg-utils.h (2)
-- Patch Links --
https://github.com/geany/geany-plugins/pull/932.patchhttps://github.com/geany/geany-plugins/pull/932.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/932
I'm afraid this might be more related to GTK than Geany itself, but still...
Most of the computers I use have a 1366x768 screen resolution, and Geany is perfectly usable in them. But one of then has a FullHD screen in which text is too small, so I have set the Windows font size to 150%. Most applications render properly, and also do other editors such as Notepad++, or IDEs such as Visual Studio, but Geany results far less readable than in the other computers, which have 1366x768 and 100% font size.
I'm using Geany 1.31 and Windows 10 (in all the computers).
--
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/1655
When using dark color schemes the pair tag highlighting completely obscures tag attributes. It will be nice if the highlight color and opacity is configurable through configuration file and/or some simple UI (e.g. similar to git-changebar plugin).
![pair_tag_highlight](https://cloud.githubusercontent.com/assets/421991/23891197/d8cb0e6e-089d-11e7-9d3a-7e9cfc8cea39.png)
--
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/issues/545
This pull request is heavily based on #645 from which it borrows the majority of the changes.
The main improvement is that this one doesn't break compatibility with GTK2 (there are macros which select the correct code path accordingly).
I also removed some cosmetic-only changes to maintain the differences as small as possible and provided a corrected code for console font selection (which was just commented out in the original pull request).
This was successfully tested on Centos 7.5 with stock development packages.
You can view, comment on, or merge this pull request online at:
https://github.com/geany/geany-plugins/pull/791
-- Commit Summary --
* Ported the 'Debugger' plugin to GTK3 while maintaining compatibility with GTK2.
-- File Changes --
M build/debugger.m4 (5)
M debugger/src/btnpanel.c (25)
M debugger/src/cell_renderers/cellrendererbreakicon.c (73)
M debugger/src/cell_renderers/cellrendererbreakicon.h (11)
M debugger/src/cell_renderers/cellrendererframeicon.c (62)
M debugger/src/cell_renderers/cellrendererframeicon.h (7)
M debugger/src/cell_renderers/cellrenderertoggle.c (9)
M debugger/src/dconfig.c (68)
M debugger/src/debug.c (49)
M debugger/src/dpaned.c (6)
M debugger/src/gui.c (4)
M debugger/src/plugin.c (4)
M debugger/src/stree.c (4)
M debugger/src/tpage.c (84)
-- Patch Links --
https://github.com/geany/geany-plugins/pull/791.patchhttps://github.com/geany/geany-plugins/pull/791.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/791
Allow platform-specific keybinding overrides. At the moment only for OS X
where the keybindings can be set inside keybindings_osx.conf. Similar
config files can be added for other platforms if needed in the future.
The only change is the new init_platform_kb() function which is called inside keybindings_init() (had to move it down a bit in the source code to avoid forward declarations but there's no other change in this function).
You can view, comment on, or merge this pull request online at:
https://github.com/geany/geany/pull/1395
-- Commit Summary --
* Add support for platform-specific keybindings
-- File Changes --
M data/Makefile.am (1)
A data/keybindings_osx.conf (1)
M src/keybindings.c (44)
-- Patch Links --
https://github.com/geany/geany/pull/1395.patchhttps://github.com/geany/geany/pull/1395.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/1395
The version of geany on xubuntu 18.04 is 1.32-2. 18.04 no longer has the gksu package. So, configuring a custom action such as gksu geany %f does not work. gksu's replacement is pkexec. I use geany extensively and it does not come with a policy file. I can create one but would like the standard product to have one.
--
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/1846