This PR adds GTK3 support to the scope plugin, but still keeps GTK2 support (in contrast to PR #697).
Some compatibility code (macros) were put in the common utils lib so that other plugins can use it on porting to GTK3. So this PR includes changes on scope AND utils.
@frlan: don't merge this - it's work in progress.
But this is **NOT working** yet. **I need help** with the build system:
How can I make scope do the following:
If build against GTK2 use libvte0.17 or newer, e.g. like this:
```
GP_CHECK_PLUGIN_DEPS([scope], [VTE],
[vte >= 0.17])
```
If build against GTK3 use libvte2.91 or newer, e.g. like this:
```
GP_CHECK_PLUGIN_DEPS([scope], [VTE],
[vte-2.91])
```
Thanks for any help in advance.
You can view, comment on, or merge this pull request online at:
https://github.com/geany/geany-plugins/pull/750
-- Commit Summary --
* scope: added GTK3 support (keeping GTK2 support)
-- File Changes --
M build/scope.m4 (1)
M scope/src/Makefile.am (6)
M scope/src/conterm.c (35)
M scope/src/plugme.c (4)
M scope/src/prefs.c (6)
M scope/src/prefs.h (6)
M scope/src/scope.c (4)
M scope/src/utils.c (11)
M utils/src/Makefile.am (9)
A utils/src/gp_gtkcompat.h (57)
A utils/src/gp_vtecompat.c (47)
A utils/src/gp_vtecompat.h (60)
-- Patch Links --
https://github.com/geany/geany-plugins/pull/750.patchhttps://github.com/geany/geany-plugins/pull/750.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/750
Version: 1.33 "built on or after 2018-02-28"
A highlighter can be chosen manually of course, but upon opening html files, Geany correctly chooses the HTML highlighter, but with HTM files, it does not.
--
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/1985
Feature Request:
You can close Messages Window.
But on Linux you can set its height to 0 also
(dragging window top frame border with mouse down to lower bar of screen).
Then the Message window is active, but you can't see its contents.
e.g. when starting Find in Files, you get some search results, but you can't see and this is irritating.
--
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/1926
```js
log.info(`Listening at ${ansi.cyan(`http://localhost:${port}/app`)}`);
```
This snippet may be odd but it is valid JavaScript. Having a template literal inside the `${}` of another template literal is valid. geany 1.33 is interpreting the backtick after `ansi.cyan(` as the end of the first template literal. Unfortunately this also causes the `//` in the URL to be interpreted as a Javascript comment so code folding is incorrect (the closing parenthesis is not seen).
For this specific issue I've just modified my code so `Listening at ` is a separate string so the call to ansi.cyan is not inside any template. In other cases such as [lit-html templates](https://polymer.github.io/lit-html/guide/writing-templates#loops-with-arraymap) nested template literals will be unavoidable.
I'm not sure if this is a scintilla bug and even if it is I see that scintilla has been updated since the release of geany 1.33 so I figure this is the correct place to start.
--
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/1984
On Debian 8 (amd64)
libgtk-2.24.25-3
libglib-2.42.1-1
I have a .c file opened in geany. I click on the `debug` tab in the lower left corner. Over on the right, I click the arrow to run. Geany crashes.
I set a breakpoint in the file. Do everything mentioned above. Geany crashes.
Both geany and the plugin were installed from the Debian 8 repo.
Should I build geany and the plugin from source? Install from backports? Any suggestions how I might get the debugger working?
--
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/491
In scope debugger, the debug | debug console window is white on black which is very difficult to read. I can use Edit | Prefs to change the background colour to white but the "foreground colour" does not affect the text colour. This remains light grey and very poor contrast against white bg.
The only other colour selector I can find is the long line marker ( vertical line ).
Is there an option to set the debug console text colour, or a hack to alter it ?
If not could someone with a little familiarity with the code point to where I can modify this in the source.
thx
--
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/671
Hello,
I have a small problem with arrow button for switching between tab document. When I click too fast on the arrow button, geany create new tab document and take me to the end. I also sometimes saw tabs overlapping too. Are there an issue with this bug ? I use geany 1.32 on Ubuntu 18.04 with gnome shell
--
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/1890