PS see [this](https://wiki.geany.org/howtos/configurebuildmenu) for how the
system works and what a "source" is.
--
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/733#issuecomment-
What the build system really needs is another source for plugins to use, but
which would not be saved by Geany. Then plugins can inject any command having
performed any transforms on them. At the moment a plugin has to remember to
put the Geany command back if it sets its own, or that command
As I am also using Geany for C development myself I have the same goal to be
able to set some project settings using the workbench plugin. But this will be
a long term goal and not happen in the near future I think.
Also, I still have to make up my mind how it is done best. In C the build
comma
I'm using Geany while writing Go code and it's vital to have some commands
(like golint and gofmt) to be launched periodically. As Geany doesn't allow me
to execute command for every CTRL+S press (or I don't know how to do that),
it's good to have an ability to write custom commands and bind the
Yes, it's not about the orange but is about the thing that inside is all
highlighted in orange and it's not correct.
I did a screenshot to show you the issue.
![schermata del 2018-04-09
23-45-20](https://user-images.githubusercontent.com/2910/38524778-164c3b50-3c50-11e8-9329-3ba9cada242b.png
I get the following warning when building the manual:
```
[WARNING] image.py:463 image
/home/kugel/dev/geany.git/doc/./images/sidebar_documents_only.png is too tall
for the frame, rescaling
[WARNING] image.py:463 image
/home/kugel/dev/geany.git/doc/./images/sidebar_documents_only.png is too tal
> I would prefer the first solution, for the second I discussed with Lex
> Trotman in Geany-Users list :
To clarify, the discussion was for a setting to expose Scintillas
`SCI_SETCARETLINEVISIBLEALWAYS(bool alwaysVisible)` setting.
--
You are receiving this because you are subscribed to this t
I wish to improve the visibility of the searched elements, I mean while using
the search window
I see two possibilities:
- Display the yellow arrow in the marker area (as when there are compilation
errors)
- Activate highlighting of the current line even when the window does not have
focus
I w
elextr approved this pull request.
LGTM
--
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/1813#pullrequestreview-110364788