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
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).
--
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
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
I would love it if the startup path would have the option of it being the last used directory. If I am writing a new file which I want to save into a directory several levels down in the directory tree, and I last used that directory, it would be nice if save would offer that directory first.
There are times when I spelunk down the directory tree, and if I am writing a new file for that directory, I do not want to have to spelunk down to that directory again. I think my deepest is 9 down. So when opening or saving files, I would like to open or save to the last used directory.
Also, how do I remove recent files from the list to the left? I do not want that as the default if no directory is entered into Startup path. It is annoying.
Please?
--
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/1492
This may apply to other versions as well, but I'm using Sierra.
The tabbed dialog boxes don't read the cursor position correctly. It's basically "move until the thing you want to click acts like you're hovering". Pulling the tab out as a separate window resolves the issue. The main editor doesn't have this issue.
--
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/1428