On 14-05-21 11:02 AM, Dimitar Zhekov wrote:
Hi,
Now that Geany 1.24[.1] is out, will we apply $subject? [1] [2]
[1] https://github.com/geany/geany/pull/274
[2] http://sourceforge.net/p/geany/bugs/943/?page=3
I like it overall, and especially deleting 1000 lines of code :),
although it's rea
Hi,
Now that Geany 1.24[.1] is out, will we apply $subject? [1] [2]
[1] https://github.com/geany/geany/pull/274
[2] http://sourceforge.net/p/geany/bugs/943/?page=3
--
E-gards: Jimmy
___
Devel mailing list
Devel@lists.geany.org
https://lists.geany.org/
On Mon, 19 May 2014 15:10:27 +1000
Lex Trotman wrote:
> The only questions I have on libpeas is:
>
> 1. what changes it requires in Geany to make Geany keybindings usable
> from libpeas loaded plugins
For the current C plugins, replacing PLUGIN_KEY_GROUP() [deprecated
since 0.19] with calls to
On 14-05-21 04:24 AM, Nick Treleaven wrote:
On 20/05/2014 10:29, Matthew Brush wrote:
Does anyone know why the plugin API was designed to use a bunch of
structures containing function pointers, hidden behind macros in
geanyfunctions.h? I found the commit where this stuff was added
initially (ie.
On 14-05-21 06:45 AM, Colomban Wendling wrote:
Le 19/05/2014 14:17, Thomas Martitz a écrit :
[...]
Sorry if I sound negative towards libpeas. I'm not fundamentally against
it. I try to objectively evaluate it, and it doesn't appear to be the
holy grail either, especially with our strong focus o
Le 19/05/2014 14:17, Thomas Martitz a écrit :
> [...]
>
> Sorry if I sound negative towards libpeas. I'm not fundamentally against
> it. I try to objectively evaluate it, and it doesn't appear to be the
> holy grail either, especially with our strong focus on maintaining the
> plugin ABI/API and e
Le 19/05/2014 07:10, Lex Trotman a écrit :
> [...]
>
> Just to be clear, libpeas only automates the bridge to the *loader*
> and the plugins, it does nothing for the interface between the
> Geany/Scintilla functions and the plugins (and neither does Thomas'
> proposal).
>
> That binding is indepe
On 20/05/2014 10:29, Matthew Brush wrote:
Does anyone know why the plugin API was designed to use a bunch of
structures containing function pointers, hidden behind macros in
geanyfunctions.h? I found the commit where this stuff was added
initially (ie. plugin ABI 2-3) but it doesn't mention why i
