Am 06.06.2018 um 16:16 schrieb Matthew Brush:
On 2018-06-06 01:53 AM, Mark O'Donovan wrote:
Hi,
Regarding https://github.com/geany/geany/issues/1870
What are people's thoughts on transitioning away from GitHub?
I personally have given GitHub a free pass up to now due to the
benefits they
Am 20.02.2018 um 18:00 schrieb Lars Paulsen:
Hello All,
I have a simple question: how can I force geany-plugins to be built
against GTK3?
I tried "CFLAGS=-dGP_GTK_VERSION_MAJOR=3 ./configure" but that did not
help. I saw the line "Geany version: 1.33 (GTK2)" in
the configure
Am 25.01.2018 um 18:27 schrieb Colomban Wendling:
Le 25/01/2018 à 04:38, Lex Trotman a écrit :
On 25 January 2018 at 22:19, Nick Treleaven wrote:
Hi,
I hadn't built Geany for a while, I found the MSYS2 build instructions with
autotools. Libtool seems incredibly slow -
Am 03.07.2017 um 12:33 schrieb Денис Феклушкин:
Hi!
I am writing D language plugin on D:
https://github.com/denizzzka/geany_dlang
This plugin isn't adds any new functionality but I planning replace
already implemented Geany functionality.
Especially, it will replace autocomplete list, tips
Am 22.06.2017 um 17:50 schrieb Lars Paulsen:
But please keep the assigned maintainers in the loop in case of
plugins inside geany-plugins.
Shouldn't they get a notification anyway from github as soon as I
place a PR?
If you prefer, I could additionally announce that PRs here in the
devel
Am 22.06.2017 um 07:17 schrieb Lars Paulsen:
Hi Lex,
> It has been pointed out that I totally avoided actually explicitly
> answering the question, yes use the new interface.
:-)
Ok, will do that. If I find the time I probably will update the one or
other existing plugin to the new interface
Am 22.06.2017 um 01:39 schrieb Lex Trotman:
The new system supports sub-plugins properly, but the developer who
was working on it has had an attack of the real world and the code
supporting it (at least for Python IIUC) is still in his personal
github. It may also be able to be extended to
Am 29.04.2017 um 02:35 schrieb Lex Trotman:
On 29 April 2017 at 09:55, Matthew Brush <mbr...@codebrainz.ca> wrote:
On 2017-04-28 02:35 PM, Thomas Martitz wrote:
Am 27.04.2017 um 22:51 schrieb Vasiliy Faronov:
Hi all,
From discussions elsewhere, such as [1], it sounds like one of the
Am 27.04.2017 um 22:51 schrieb Vasiliy Faronov:
Hi all,
From discussions elsewhere, such as [1], it sounds like one of the
things holding back Geany development right now is a need for more
testing.
Helping to test PRs is truly needed, and much appreciated.
However, I do think that Geany
Am 16.02.2017 um 15:55 schrieb Matthew Brush:
On 2017-02-16 03:15 AM, Thomas Martitz wrote:
Am 16.02.2017 um 11:58 schrieb Vasiliy Faronov:
Jiří, Matthew, thanks!
I missed the GKeyFile thing.
Actually, my plugin is written in Python (via Geanypy), and doesn't
get the GKeyFile on project-open
Am 01.09.2016 um 15:00 schrieb Lex Trotman:
[...]
It is of course always "possible", after all its a mere matter of
programming :)
And of course an instantiated class template is just a type, but what
is the name of std::vector and std::vector so it can be looked
up?
vector and vector, with
Am 01.09.2016 um 07:47 schrieb Matthew Brush:
On 2016-08-31 10:08 PM, Thomas Martitz wrote:
Am 31.08.2016 um 17:26 schrieb Lex Trotman:
I think we all agree that help of language-specific plugins is
desired/required. No need to restate "we need language specific
support" all
the time
Am 01.09.2016 um 08:05 schrieb Lex Trotman:
On 1 September 2016 at 15:08, Thomas Martitz <ku...@rockbox.org> wrote:
Am 31.08.2016 um 17:26 schrieb Lex Trotman:
I think we all agree that help of language-specific plugins is
desired/required. No need to restate "we need language speci
Am 01.09.2016 um 07:17 schrieb Matthew Brush:
On 2016-08-31 09:57 PM, Thomas Martitz wrote:
Am 01.09.2016 um 02:50 schrieb Matthew Brush:
I don't think they'll usually require a "build system" per se, but
they definitively need to be told how to compile the code where
Am 01.09.2016 um 05:42 schrieb Lex Trotman:
On 31 August 2016 at 11:27, Matthew Brush wrote:
With the `LexClang.so` dynamic lexer I made, dynamic lexers seemed not to
fit well (too isolated, too many assumptions that it's a simple dumb lexer
and not a semantic-based on,
Am 31.08.2016 um 16:52 schrieb Lex Trotman:
On 1 September 2016 at 00:43, Thomas Martitz <ku...@rockbox.org> wrote:
Am 31.08.2016 um 16:39 schrieb Matthew Brush:
I can't speak to all compiler libraries, but at least libclang, libpython
and libvala "compile" the source (well ju
Am 31.08.2016 um 15:31 schrieb Lex Trotman:
I love Lex's ADL example, C++ can seem just crazy :)
Crazy like a Fox, makes the compiler near impossible, but makes lots
of stuff "just work" :)
So a much simpler example then (using C syntax to explain since we all
know it, but could be any
Am 31.08.2016 um 16:39 schrieb Matthew Brush:
I can't speak to all compiler libraries, but at least libclang,
libpython and libvala "compile" the source (well just the front-end of
the compiler is needed). They literally use the built-in compiler
front ends to understand the code. In the
Am 31.08.2016 um 13:23 schrieb Lex Trotman:
[...]
But
to be able to do 2) and 3) accurately needs more knowledge of each
language semantics than is currently available in Geany or tagmanager.
That's right. But it doesn't mean the features should be *entirely* moved
into plugin space. TM
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
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
Am 30.08.2016 um 03:56 schrieb Lex Trotman:
On 29 August 2016 at 22:38, Thomas Martitz <ku...@rockbox.org> 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 sing
Am 29.08.2016 um 17:05 schrieb Jiří Techet:
The solution I have in mind simply allows plugins to pass tags to
Geany which they parsed with more advanced code. The tags itself
would advanced too, to allow for the improvements current TM+ctags
can't offer. Symbol tree, calltips,
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
the plugins. That's just making it harder (maybe impossible?) to change or add
use cases.
The
Am 29.08.2016 um 05:14 schrieb Matthew Brush:
Hi All,
Related to my previous mail, and assuming it is somewhat reasonable, I
would like to propose a list of initial features that will be useful
to allow plugins to provide, in no particular order:
I disagree with this approach. This adds
Uhm, where did this thread start? Who are you replying to?
Am 26.08.2016 um 09:13 schrieb Lex Trotman:
Not sure I agree that Github is bad for *development* discussions, for
users, sure, the ML is likely to find the audience better, but most
developers will also be githubians. Also github
Hello,
more than two years after my initial message "RFC: Proxy plugins" I've
finally
reached the point that I envisioned back then. As a result, I can now
release
Peasy, which is my first personal proxy plugin, which I'm taking seriously.
Please give me feedback or even contribute to this
Am 11.08.2016 um 00:34 schrieb Colomban Wendling:
Also, for the moment you pretty much need to write Geany
plugins in C or C++, although Thomas' Peasy plugin [1] adds support for
several languages (include JS I'd believe), and it's getting closer to
stability.
What about
Am 24. März 2016 16:21:00 MEZ, schrieb "Jiří Techet" :
>>
>>
>>> That's it then. If you run Windows in VM on a "retina" Mac where
>each
>> original pixel consists of 4 smaller pixels then 100% is just
>unusable
>> because everything is too small. I can imagine 4k screen with 100%
Am 23.03.2016 um 15:21 schrieb Jiří Techet:
Some problems I noticed with the Gtk 3 build:
- any file dialog like File->Open, Project->open, File->Save as etc.
crashes Geany on my machine
I think I had this happen when one of the post-install scripts (of glib
iirc) wasn't run when creating
Am 07.01.2016 um 23:00 schrieb Jiří Techet:
On Wed, Jan 6, 2016 at 9:23 PM, Thomas Martitz <ku...@rockbox.org
<mailto:ku...@rockbox.org>> wrote:
Am 06.01.2016 um 21:12 schrieb Jiří Techet:
It's indeed at least interesting to consider, because at
Am 06.01.2016 um 12:39 schrieb Matthew Brush:
On 2016-01-06 02:44 AM, Thomas Martitz wrote:
Am 06.01.2016 um 04:32 schrieb Matthew Brush:
Agree, I sometimes avoid putting LGTM when I think something is a good
idea, because I don't want to give the impression that I have (or even
Am 06.01.2016 um 12:47 schrieb Lex Trotman:
I can't put labels on github. The feature seems to be limited to those with
write access to the repository, so it's useless if we want more reviewers.
Please just add a comment, its actually clearer anyway since we don't
have a well defined semantics
Am 06.01.2016 um 21:12 schrieb Jiří Techet:
It's indeed at least interesting to consider, because at least for .h
headers there really is some mixed stuff all over the place -- even,
simply look in Scintilla's source tree.
+1 for having the headers parsed/lexed by the C++ parser
Am 21.11.2015 um 14:42 schrieb Frank Lanitz:
Hi folks,
Since a few releases I'm experiencing some not optimal way of
development which is surely caused by the long history we already have
on g-p as well as by the many people around luckily contributing to the
plugins collection: More and more
Am 04.11.2015 um 23:55 schrieb Colomban Wendling:
On 04/11/2015 22:21, Enrico Tröger wrote:
On 04/11/15 14:19, Colomban Wendling wrote:
Re the build failures: yeah, since a few days we can't seem to
fetch the GTK3 bundle… it's not a biggie in practice as if all of
Linux+GTK2, Linux+GTK3 and
Am 01.11.2015 um 18:50 schrieb Colomban Wendling:
Also, IMO a replacement/large improvement should include the following
in the end:
1. Seamless integration (all features in all splits)
2. (keep) support for multiple views of the same document
3. multiple (arbitrary) splits
Point 1 is obvly
Am 31. Oktober 2015 11:39:21 MEZ, schrieb Abel :
I understand. I'm trying to solve the inconsistency of being editing a
document on split window but having the status bar showing something
else
(Should I open a issue to report this bug?). So, yes, you can take this
as
a
Am 31.10.2015 um 18:59 schrieb Matthew Brush:
On 15-10-31 02:08 AM, Thomas Martitz wrote:
Am 31. Oktober 2015 02:52:01 MEZ, schrieb Matthew Brush
<notificati...@github.com>:
[...] so unless there are actual problems I don't see an evidence to
keep the off default.
I mentioned a
Am 24.10.2015 um 02:30 schrieb Matthew Brush:
FWIW, doc->id is basically not very useful, it just tells the index
into some internal array of GeanyDocument objects, but is not unique
to each document/tab per se (it gets recycled for new documents and
such).
doc->id is unique these days,
Am 20.08.2015 um 01:25 schrieb Matthew Brush:
On 15-08-19 04:20 PM, Oliver Krystal wrote:
Yes, I'm subscribed. Well, I use to be the developer but the facts
should still hold true. PortableApps.com doesn't modify the source
code, but uses a wrapper around the program to achieve portable-ness.
Am 09.07.2015 um 18:00 schrieb Steven Blatnick:
Responses below:
On 07/08/2015 11:23 PM, Thomas Martitz wrote:
Remember that plugin_set_key_group() can be called repeatedly.
Calling it again will simply clear all existing keybindings, then you
can start over again with keybindings_set_item
Am 09.07.2015 um 04:28 schrieb Steve:
On Jul 8, 2015 7:18 PM, Matthew Brush mbr...@codebrainz.ca wrote:
On 2015-07-08 10:57 AM, Steven Blatnick wrote:
So I've finally got a chance to look at my non-API calls. I was able to
code around most of them, but there are two that would be much easier
Weitergeleitete Nachricht
Betreff: Re: Github loses comments
Datum: Tue, 07 Jul 2015 00:29:38 -0700
Von: Ivan Žužak supp...@github.com
An: Thomas Martitz ku...@rockbox.org
Hi Thomas,
Thanks for sharing those details about your workflow.
If you create a comment on a commit
Hello,
first of all, I think github should fix this problem, instead of
enforcing a suboptimal workflow on us.
I reported this problem to github, let's see if they respond.
Am 07.07.2015 um 02:13 schrieb Matthew Brush:
Hi All,
As anyone trying to follow Pull Requests on Github has probably
Am 01.07.2015 um 21:33 schrieb Enrico Tröger:
On 27/06/15 20:53, Thomas Martitz wrote:
Am 27.06.2015 um 01:09 schrieb Enrico Tröger:
Hi,
I've built new Windows installers from current GIT master.
Downloads can be found here:
http://download.geany.org/snapshots/
Please note
Am 29.06.2015 um 00:32 schrieb Lex Trotman:
On 29 June 2015 at 07:41, Colomban Wendling lists@herbesfolles.org wrote:
Le 26/06/2015 07:22, Thomas Martitz a écrit :
[…]
However, as we entered string freeze, I don't suppose a new dialog like
this is acceptable at this point?
It would
Am 28.06.2015 um 12:36 schrieb Enrico Tröger:
On 27/06/15 20:53, Thomas Martitz wrote:
Am 27.06.2015 um 01:09 schrieb Enrico Tröger:
Hi,
I've built new Windows installers from current GIT master.
Downloads can be found here:
http://download.geany.org/snapshots/
Please note
Am 26.06.2015 um 07:22 schrieb Thomas Martitz:
Hello,
I hacked up a document message to inform the user about this new
behavior, see attached screenshot.
However, as we entered string freeze, I don't suppose a new dialog
like this is acceptable at this point? What else can we do
Am 28.06.2015 um 05:14 schrieb Matthew Brush:
On 2015-06-27 07:54 PM, Lex Trotman wrote:
On 28 June 2015 at 12:40, Matthew Brush mbr...@codebrainz.ca wrote:
On 2015-06-27 12:46 PM, Dimitar Zhekov wrote:
[...]
An updated list of the API-s asked to remain public:
meWIF*
lex
Am 28.06.2015 um 21:30 schrieb Thomas Martitz:
Am 28.06.2015 um 20:39 schrieb Colomban Wendling:
Le 03/07/2012 20:15, Enrico Tröger a écrit :
[…]
If someone have more information about available builds (and a related
-dev package) I might have a look though I doubt we'll manage
Am 28.06.2015 um 20:39 schrieb Colomban Wendling:
Le 03/07/2012 20:15, Enrico Tröger a écrit :
[…]
If someone have more information about available builds (and a related
-dev package) I might have a look though I doubt we'll manage that for
the 1.22 release which is, AFAIK, due on upcoming
Am 27.06.2015 um 01:09 schrieb Enrico Tröger:
Hi,
I've built new Windows installers from current GIT master.
Downloads can be found here:
http://download.geany.org/snapshots/
Please note that these are test builds from the current development
version, don't expect release quality.
You have
Hello,
I hacked up a document message to inform the user about this new
behavior, see attached screenshot.
However, as we entered string freeze, I don't suppose a new dialog like
this is acceptable at this point? What else can we do for *this* release?
Best regards
Am 24.06.2015 um 22:26 schrieb Lex Trotman:
I'm struggling to understand why there is any confusion, reload is an
editing action just like any other and can be undone like any other.
Seems much safer to me and exactly what to expect. It used to have a
side effect that was unexpected and nasty
Hello
I have just noticed that current git, by default, doesn't prompt anymore
when reloading documents, even when they are changed.
I traced it back to the $SUBJECT commit. IMO it's fine to keep the undo
history on reload and not prompt, but it's not fine if the file is
currently modified
Am 24.06.2015 um 18:30 schrieb Colomban Wendling:
Le 24/06/2015 17:04, Thomas Martitz a écrit :
Hello
I have just noticed that current git, by default, doesn't prompt anymore
when reloading documents, even when they are changed.
I traced it back to the $SUBJECT commit. IMO it's fine to keep
Am 14.06.2015 um 13:59 schrieb Enrico Tröger:
On 07/06/15 22:31, Thomas Martitz wrote:
Am 7. Juni 2015 17:53:36 MESZ, schrieb Yury Siamashka yura...@gmail.com:
05/29/15 12:00, Thomas Martitz пишет:
Hello,
I've successfully managed to build Geany on MSYS2, against both gtk2
and gtk3. I've
Am 14.06.2015 um 14:48 schrieb Enrico Tröger:
On 14/06/15 14:21, Thomas Martitz wrote:
Why do you say self-compiled GTK? It is readily packaged for msys, I
think we should be able to use that.
Oops, scratch the self-compiled. But we still need to create a
distributable GTK runtime environment
Am 14.06.2015 um 16:48 schrieb Enrico Tröger:
At some point we had some discussion whether to use the same directory
on Windows as on Unix but I don't know the result.
We do this already don't we (except for the renamed text files)?
need to install to a special directory?
The current
Am 14.06.2015 um 18:26 schrieb Enrico Tröger:
This is why :).
I thought a couple of times of making geany.nsi.in and
geany_private.rc.in and fill in the version number automatically. But I
never was annoyed enough to fiddle with the 4-part version numbers used
there. Maybe you are :).
The
Am 14.06.2015 um 16:35 schrieb Enrico Tröger:
On 14/06/15 15:50, Thomas Martitz wrote:
Am 14.06.2015 um 14:48 schrieb Enrico Tröger:
On 14/06/15 14:21, Thomas Martitz wrote:
Why do you say self-compiled GTK? It is readily packaged for msys, I
think we should be able to use that.
Oops
Am 14.06.2015 um 18:32 schrieb Thomas Martitz:
Actually the issue goes away if I remove the installer-included GTK
runtime, so that the one in PATH is used. I guess I didn't add enough
files (icons?) to the installer
Indeed, I could fix the lacking icons and the warning spam
Am 14.06.2015 um 23:20 schrieb Enrico Tröger:
On 14/06/15 19:08, Thomas Martitz wrote:
Am 14.06.2015 um 18:32 schrieb Thomas Martitz:
Actually the issue goes away if I remove the installer-included GTK
runtime, so that the one in PATH is used. I guess I didn't add enough
files (icons
Am 14.06.2015 um 17:44 schrieb Enrico Tröger:
On 14/06/15 17:16, Thomas Martitz wrote:
Am 14.06.2015 um 16:55 schrieb Thomas Martitz:
Am 14.06.2015 um 16:48 schrieb Enrico Tröger:
At some point we had some discussion whether to use the same directory
on Windows as on Unix but I don't know
Am 7. Juni 2015 17:53:36 MESZ, schrieb Yury Siamashka yura...@gmail.com:
05/29/15 12:00, Thomas Martitz пишет:
Hello,
I've successfully managed to build Geany on MSYS2, against both gtk2
and gtk3. I've started to describe the steps on the wiki:
https://wiki.geany.org/howtos/win32/msys2
Am 30.05.2015 um 03:19 schrieb Matthew Brush:
Just because it's such a trivial search algorithm, using strstr() is
much more simple and probably more efficient than using Scintilla's
API to find text, but if manual and automatic mode is supported, it
would make sense to share the existing
Am 27.05.2015 um 14:25 schrieb marius buzea:
Hello,
I would like to add GeanyHighlightSelectedWords, to Geany Plugins.
Would it be okay that I do a git pull-request for doing this? I
am the mgnt user on sourceforge, and last week there was a ticket
added to GeanyHighlightSelectedWords, ticket
Am 25. April 2015 05:22:38 MESZ, schrieb Colomban Wendling
lists@herbesfolles.org:
So yeah, if anyone wishing to keep on using this plugin should consider
helping maintaining it, it really needs some love from time to time.
Libpeas includes lua support as of v1.14. So if my whole proxy
Am 19.04.2015 um 15:57 schrieb Enrico Tröger:
This said, the reason we need the hack is because of
https://bugzilla.gnome.org/show_bug.cgi?id=712220, so if this was fixed
we could one day drop the hack. But this would mean depend on a fixed
version, which probably won't be acceptable before a
Am 16.04.2015 um 23:20 schrieb Colomban Wendling:
Is a pref necessary?
Yes.
In that case it's not the best solution and we should find an indication that
people don't want to outright disable.
The underline gets the job done but I'm not married to it. Can you suggest a
better alternative?
Am 16.04.2015 um 21:47 schrieb Enrico Tröger:
On 16/04/15 18:47, Dimitar Zhekov wrote:
On 16.4.2015 г. 12:37, Thomas Martitz wrote:
Am 15.04.2015 um 19:15 schrieb Dimitar Zhekov:
That's exactly what I'm talking about. The white horizontal line,
which normally gives nice outline [vertical_tabs
Am 29.03.2015 um 18:19 schrieb Colomban Wendling:
So anyway, I think I'd be in favor of a failable init(), maybe like
gboolean (*init) (..., GError **error); if we want to be able to
report messages and the like. Or just let each plugin do the same
msgwing_add() or whatever, but a common
Am 30.03.2015 um 23:07 schrieb Thomas Martitz:
Am 30.03.2015 um 14:57 schrieb Colomban Wendling:
If `pdata` is provided in geany_plugin_register(), how does it get
released? If it has to be a pointer to static data it's a bit limiting,
and forces use of (static) globals, which is one thing
useful when they are needed, like GtkDialog*
for configure.
Le 28/03/2015 23:56, Thomas Martitz a écrit :
[…]
geany_load_module(), which is called by Geany via pointer obtained from
g_module_symbol(). In this function the plugin should perform the
following steps:
- Test against the passed
Am 30.03.2015 um 14:33 schrieb Lex Trotman:
What is is_plugin()? If its a function in Geany how does it get to
know about new types of plugins without being hard coded?
It knows because the extensions are registered by the function below
called by another plugin right? How do you make sure
Hello,
some if your question are easier to answer by looking at the code, I'll
link the appropriate sections.
Am 30.03.2015 um 13:16 schrieb Lex Trotman:
[...]
Ok, this explains some of what I was asking on the other thread, so
now I can ask the more specific questions below that are the
Am 30.03.2015 um 19:18 schrieb Colomban Wendling:
Hi,
What do you think?
Is this a real problem (reported by someone) or just theoretical?
Unless there is actually a real problem caused by this for someone I'd
vote for not doing anything. After all, somone naming his files `foo
bar.c`
Am 30.03.2015 um 14:57 schrieb Colomban Wendling:
If `pdata` is provided in geany_plugin_register(), how does it get
released? If it has to be a pointer to static data it's a bit limiting,
and forces use of (static) globals, which is one thing that this new API
tries to avoid, doesn't it? We
Am 29.03.2015 um 05:20 schrieb Lex Trotman:
Thomas,
Thanks for that, it now makes it clearer where you are going, and
allows the individual steps to make more sense.
I agree with your four problems (shortened):
- linkage
- keybindings
- plugin context
- allow for proxies
My concern is that
Am 29.03.2015 um 19:17 schrieb Colomban Wendling:
Le 29/03/2015 00:23, Thomas Martitz a écrit :
- New API functions to allow plugins to act as proxy plugins (pluxies).
These pluxies can then implement whatever is needed to execute code in
the in the actual plugin, like invoking an interpreter
Hello,
based on the discussion I refined my proposal (see below). Additionally
I have implemented all of this, including updating demoplugin.c, see
[1]. And last but not least, I have a fully working implementation of
proxy plugins aka pluxies (in fact, I simply updated my year-old branch
to
Am 26.03.2015 um 18:47 schrieb Dimitar Zhekov:
On 26.3.2015 г. 01:16, Thomas Martitz wrote:
Now, do we really want the plugins to run arbitrary resource checking
code, and display their own error messages, only because they are
queried (or registered, as you put it), each time the list
Am 20.03.2015 um 19:45 schrieb Dimitar Zhekov:
Thinking about it, if the plugin can't run because it's missing resource
files required for its operation, then I think it should be treaded like
incompatible plugins.
There seem like two different things to me.
The first thing a loader needs
Am 18.03.2015 um 22:55 schrieb Matthew Brush:
On 15-03-18 09:42 AM, Thomas Martitz wrote:
tl;dr -
Key functions
gboolean geany_load_module(GeanyPlugin *, GModule *)
What is the GModule* for? Is it a .dll that Geany opened on behalf of
the plugin based on selection in Plugin Manager
Am 19.03.2015 um 23:34 schrieb Lex Trotman:
On 19 March 2015 at 09:16, Thomas Martitz ku...@rockbox.org wrote:
There is no other way of loading C shared libraries and registering them as
plugins.
Doesn't Geany already load dlls local and extract the symbols it wants
via dlsym()?
dlsym() takes
Am 19.03.2015 um 01:19 schrieb Matthew Brush:
On 15-03-18 03:55 PM, Thomas Martitz wrote:
Am 18.03.2015 um 23:21 schrieb Matthew Brush:
On 15-03-18 03:05 PM, Thomas Martitz wrote:
Am 18.03.2015 um 22:15 schrieb Matthew Brush:
[...]
void (*init) (GeanyPlugin *plugin, gpointer pdata
Hello,
tl;dr - scroll down
I am working on a new plugin architecture that deals with some of the
shortcomings of the current state. My primary motivation is to be able
to use libpeas to load plugins, both C and non-C (Python!), as you might
have learned from other threads I started. However
Am 18.03.2015 um 21:23 schrieb Dimitar Zhekov:
On 18.3.2015 г. 18:42, Thomas Martitz wrote:
- Global symbols. Plugins binaries have to export a number of global
symbols (geany_{functions,data,plugin}, plugin_{init,...,cleanup}). This
kind of sucks, because they pollute the global namespace
shortcomings:
On 03/18/2015 10:42 AM, Thomas Martitz wrote:
Currently geany exports a pointer to a struct, that contains more
structs, which contain function points to the API functions.
Fortunately this is nicely hidden to developers via macros. But due
to gtkbuilder all functions and nothing prevents
Am 18.03.2015 um 23:21 schrieb Matthew Brush:
On 15-03-18 03:05 PM, Thomas Martitz wrote:
Am 18.03.2015 um 22:15 schrieb Matthew Brush:
[...]
void (*init) (GeanyPlugin *plugin, gpointer pdata);
Please make this gboolean. A plugin may have the correct API and ABI,
but be unable to startup
Am 18.03.2015 um 22:23 schrieb Lex Trotman:
Hi Thomas,
In general this looks like an improvement to the current method of
setting up plugins, except it continues to require the plugin .so file
to be dlloaded just to populate the plugin manager. That will run the
dll initialization code, and
Am 18.03.2015 um 22:15 schrieb Matthew Brush:
[...]
void (*init) (GeanyPlugin *plugin, gpointer pdata);
Please make this gboolean. A plugin may have the correct API and ABI,
but be unable to startup / initialize for some reason. For example,
Scope requires scope.glade in the plugin data
Am 11.07.2014 um 22:03 schrieb Colomban Wendling:
Le 07/07/2014 18:48, Thomas Martitz a écrit :
[...]
In my last post I've followed the approach of proxy plugins, aka pluxys.
This approach is based on geanypy and implements a plugin API for
plugins to act as proxy. I have mostly finished
Am 23.10.2014 um 04:11 schrieb Matthew Brush:
On 14-10-22 06:53 PM, Lex Trotman wrote:
On 23 October 2014 11:53, Matthew Brush mbr...@codebrainz.ca wrote:
Hi All,
Since there's some discussion about infobar behaviour, I thought I'd
mention
a couple things I've noticed using it in my
Am 13.10.2014 15:21, schrieb Colomban Wendling:
Le 13/10/2014 08:06, Thomas Martitz a écrit :
Hi,
this is about commit ab7a0018b2518793f26af2fe20a06a8a1886e031 and the
message reads
Don't prompt for reload from infobar when there are no unsaved changes.
The patch removes the confirmation
Hi,
this is about commit ab7a0018b2518793f26af2fe20a06a8a1886e031 and the
message reads
Don't prompt for reload from infobar when there are no unsaved changes.
What does that mean? I do absolutely want to be asked before reloading
even if the file has no changes or saved ones.
Best
Am 21.09.2014 um 15:48 schrieb Dimitar Zhekov:
Hi,
Since Debian is leaning more and more towards systemd, especially with
gvfs installed, and since systemd-init breaks my system, I finally sat
on my back and migrated to Windows. It's not a good system either, but
gets the job done.
Now,
Hello,
I proposed a patch for scintilla, to make it more g-ir-scanner-friendly.
If you want to chime in, or if this patch conflicts with Geany in a way
that I'm not aware of, please join the fun.
https://groups.google.com/d/msg/scintilla-interest/Z7lk3SkBkxs/nHIHPGYCgbkJ
Best regards
Am 12.07.2014 01:35, schrieb Lex Trotman:
On 12 July 2014 09:25, Matthew Brush mbr...@codebrainz.ca wrote:
On 14-07-11 01:25 PM, Thomas Martitz wrote:
Am 11.07.2014 22:03, schrieb Colomban Wendling:
Le 07/07/2014 18:48, Thomas Martitz a écrit :
[...]
In my last post I've followed
1 - 100 of 164 matches
Mail list logo