@kugel- yay, built a new clone, Geany works and nothing in `$PREFIX/lib`.
:smile:
Geany-plugins (at least the ones I have dependencies for) built and installed
in `lib/x86_64-linux-gnu` except for `pluginutils` that spammed `/lib`, but
thats not this PRs problem. At least debugger (which
@eht16 pushed 1 commit.
dc4bb325bdc1bba80d042eb9d6536fc34f94635e Run Linux builds on Ubuntu 18.04 (as
it was before)
--
You are receiving this because you are subscribed to this thread.
View it on GitHub:
@eht16 pushed 1 commit.
f24c4245d0869c4ab782525f1719df278baeafb5 Run Linux builds on Ubuntu 18.04 (as
it was before)
--
You are receiving this because you are subscribed to this thread.
View it on GitHub:
@xiota pushed 1 commit.
55fa60e16ed13a5ae5aab4759c824f1206a9fd50 remove unnecessary variables
--
You are receiving this because you are subscribed to this thread.
View it on GitHub:
@xiota pushed 1 commit.
0a25afc920cae77f254676fdf717663a402a9bdc fix project filename matching
--
You are receiving this because you are subscribed to this thread.
View it on GitHub:
@xiota pushed 1 commit.
8706b29cb7daa5a6bc59153f235150c091ae0824 Initialize some char pointers to NULL
--
You are receiving this because you are subscribed to this thread.
View it on GitHub:
@elextr I just looked at `glspi_sci.c`... looks like new return types will
need to be added. Will look into blocking the LEX messages while doing that.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
Ultimately the Geany devs only advise plugin writers, we are not responsible
for plugin content, just the collection infrastructure. So long as the plugin
doesn't crash Geany its normally up to the plugin maintainer, but as the plugin
is orphaned, I guess its up to you if you want to pass the
@elextr So I learned this file is autogenerated...
> But catching signals is fine, its what you do when you get it that matters.
You want the plugin modified to block/ignore scintilla messages of the form
`[A-Z]+_SET[A-Z]?LEX[A-Z_]+`? Or just let it be on the plugin user to write
sensible
@xiota commented on this pull request.
> @@ -69,6 +69,8 @@ typedef struct GeanyInterfacePrefs
gbooleancompiler_tab_autoscroll;
gintmsgwin_orientation; /**<
orientation of the message window */
gint
@xiota pushed 1 commit.
744dc2053471f0cb2a74a2ccf3842a78b00e5176 Correct documentation comment
--
You are receiving this because you are subscribed to this thread.
View it on GitHub:
@xiota commented on this pull request.
> @@ -631,8 +631,13 @@ static void handle_input_filename(const gchar *buf)
{
if (g_str_has_suffix(locale_filename, ".geany"))
{
- if (project_ask_close())
-
@xiota pushed 1 commit.
53704f19283f4b1afa97c631cc6268b68f9d6d64 convert locale of project filename
before comparison
--
You are receiving this because you are subscribed to this thread.
View it on GitHub:
@elextr commented on this pull request.
> @@ -69,6 +69,8 @@ typedef struct GeanyInterfacePrefs
gbooleancompiler_tab_autoscroll;
gintmsgwin_orientation; /**<
orientation of the message window */
gint
@elextr commented on this pull request.
> @@ -69,6 +69,8 @@ typedef struct GeanyInterfacePrefs
gbooleancompiler_tab_autoscroll;
gintmsgwin_orientation; /**<
orientation of the message window */
gint
@xiota if a plugin modifies _any_ Scintilla/Lexilla or other setting that Geany
uses it can upset how Geany uses it, or the value the plugin sets could be
overwritten by Geany at any point, possibly breaking the plugin. Geany simply
does not know about what plugins do outside the documented
@xiota commented on this pull request.
> @@ -69,6 +69,8 @@ typedef struct GeanyInterfacePrefs
gbooleancompiler_tab_autoscroll;
gintmsgwin_orientation; /**<
orientation of the message window */
gint
@Skif-off Thanks. I should read those comment blocks at the beginning of
files. Got used to them being copyright messages.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
@xiota pushed 1 commit.
febc7dd6bd2b6106844d1563af66eafe9be61481 GeanyLua: Use util/mkiface.lua to
generate new glspi_sci.h
--
You are receiving this because you are subscribed to this thread.
View it on GitHub:
@elextr So all the lexer signals should be removed?
--
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/1123#issuecomment-947408086
@elextr commented on this pull request.
> @@ -69,6 +69,8 @@ typedef struct GeanyInterfacePrefs
gbooleancompiler_tab_autoscroll;
gintmsgwin_orientation; /**<
orientation of the message window */
gint
@elextr commented on this pull request.
> @@ -631,8 +631,13 @@ static void handle_input_filename(const gchar *buf)
{
if (g_str_has_suffix(locale_filename, ".geany"))
{
- if (project_ask_close())
-
Even if it could be added, `setilexer` probably shouldn't, if a plugin sets a
lexer directly it is likely to break lots of filetype things that depend on the
known lexer, set the filetype via Geany which will set the appropriate lexer,
not the lexer directly.
--
You are receiving this because
@Skif-off then you don't need `SETILEXER` since the pointer that you pass to it
can only be obtained from the lexilla interface.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
@elextr
> need to map Lexilla as well as Scintilla
Why? GeanyLua uses the Scintilla interface, also all SCI_*LEXER* will be
available.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
25 matches
Mail list logo