On 2016-08-30 06:43 AM, Colomban Wendling wrote:
Le 29/08/2016 à 05:14, Matthew Brush a écrit :
[…]
Syntax Highlighting
---
Most likely using an API based on/similar to Scintilla's "container
lexers".
At the minimum, it could have a callback something like:
gboolean (*hig
On 2016-08-30 06:38 AM, Colomban Wendling wrote:
Le 29/08/2016 à 10:04, Jiří Techet a écrit :
[…]
Which brings me to a question - do you plan to generate TMTag(s) and
feed them to the tag manager instead of the ctags ones? It shouldn't be
that hard and if you do this, you could have the sideb
On 2016-08-30 06:29 AM, Colomban Wendling wrote:
Le 29/08/2016 à 03:09, Matthew Brush a écrit :
On 2016-08-28 05:47 PM, Matthew Brush wrote:
[...]
To give an idea, the registration function called by plugins might look
something like this:
gboolean ftplugin_register_provider(GeanyPlugin*,
On 2016-08-30 06:24 AM, Colomban Wendling wrote:
Le 29/08/2016 à 02:47, Matthew Brush a écrit :
[…]
To give an idea, the registration function called by plugins might look
something like this:
gboolean ftplugin_register_provider(GeanyPlugin*,
GeanyFiletypeID, GeanyFiletypeFeature,
On 2016-08-30 02:29 PM, Thomas Martitz wrote:
Am 30.08.2016 um 21:10 schrieb Jiří Techet:
[...]
And even if we did this, I don't know how we could handle ASTs of
different languages in a generic way because these will differ
significantly.
One more time, seems I wasn't clear enough yet: I'm
Am 30.08.2016 um 21:10 schrieb Jiří Techet:
Geany would then merge the tags, perhaps giving the plugin
ones more
weight, and store it in TM.
I think you underestimate how many tags we're talking here. The
example libclang ft-plugin would have to re-walk the enti
On Tue, Aug 30, 2016 at 6:41 PM, Matthew Brush wrote:
> On 2016-08-30 08:51 AM, Thomas Martitz wrote:
>
>> Am 30.08.2016 um 01:53 schrieb Matthew Brush:
>>
>>> On 2016-08-29 03:17 PM, Thomas Martitz wrote:
>>>
Am 29.08.2016 um 17:05 schrieb Jiří Techet:
> [...]
>
There
On 2016-08-30 08:51 AM, Thomas Martitz wrote:
Am 30.08.2016 um 01:53 schrieb Matthew Brush:
On 2016-08-29 03:17 PM, Thomas Martitz wrote:
Am 29.08.2016 um 17:05 schrieb Jiří Techet:
[...]
There is also another aspect about the proposal that worries me: a
plugin shall provide N features for M
Le 30/08/2016 à 17:31, Thomas Martitz a écrit :
> Am 30.08.2016 um 03:56 schrieb Lex Trotman:
>>> […]
>
>> Certainly 1) showing symbols in the symbol list, 2) autocomplete and
>> 3) calltips are currently available to a degree in Geany. But
>> highlighting, build commands and build result handlin
Am 30.08.2016 um 01:53 schrieb Matthew Brush:
On 2016-08-29 03:17 PM, Thomas Martitz wrote:
Am 29.08.2016 um 17:05 schrieb Jiří Techet:
[...]
There is also another aspect about the proposal that worries me: a
plugin shall provide N features for M languages. And X plugins might be
compete (not
Am 30.08.2016 um 15:38 schrieb Colomban Wendling:
Which brings me to a question - do you plan to generate TMTag(s) and
feed them to the tag manager instead of the ctags ones? It shouldn't be
that hard and if you do this, you could have the sidebar symbols updated
for free.
I don't know if plug
Am 30.08.2016 um 03:56 schrieb Lex Trotman:
On 29 August 2016 at 22:38, Thomas Martitz wrote:
Am 29.08.2016 um 14:23 schrieb Lex Trotman:
This adds per use case hooks to plugins, which then became part of the
stable API. I don't think that we have to codify every single use case of
tags into t
Le 29/08/2016 à 05:14, Matthew Brush a écrit :
> […]
>
> Syntax Highlighting
> ---
>
> Most likely using an API based on/similar to Scintilla's "container
> lexers".
>
> At the minimum, it could have a callback something like:
>
> gboolean (*highlight)(GeanyPlugin*, GeanyDoc
Le 29/08/2016 à 10:04, Jiří Techet a écrit :
> […]
>
> sounds good. This is much more lightweight than how #1195 and various
> other discussions sounded, I'm happy :-).
Agreed :) I was a little afraid of seeing a proposal introducing a
gazillion GObject interfaces and GIO extension points ^^
>
Le 29/08/2016 à 03:09, Matthew Brush a écrit :
> On 2016-08-28 05:47 PM, Matthew Brush wrote:
>> [...]
>>
>> To give an idea, the registration function called by plugins might look
>> something like this:
>>
>> gboolean ftplugin_register_provider(GeanyPlugin*,
>> GeanyFiletypeID, GeanyF
Le 29/08/2016 à 02:47, Matthew Brush a écrit :
> […]
>
> To give an idea, the registration function called by plugins might look
> something like this:
>
> gboolean ftplugin_register_provider(GeanyPlugin*,
> GeanyFiletypeID, GeanyFiletypeFeature, GCallback, gpointer);
Maybe we could
16 matches
Mail list logo
