Hi Plugins-Devs,
As you might did see I did some work during the weekend to fix make
check (and break it during this also again ;) ) as well as did some
minor code changes where I thought they don't hurt much but would
improve something.
However, I recognized tons of compiler warnings which
On 04/28/11 00:01, Frank Lanitz wrote:
Hi,
Am 12.03.2011 19:11, schrieb Frank Lanitz:
During the last weeks a huge number mails at this list was stating to
make usage of GObject on building up a new plugin interface. It has been
talked about libpeas and adding support for Vala, Python etc.
On 04/28/11 00:10, Frank Lanitz wrote:
However, I recognized tons of compiler warnings which did make me upset.
I know, many of them might not be any dangerous but I really like to ask
you to to have a look onto it and fix where possible/useful.
My plugin's 'make check' output, unlike its
Hi,
I started working on merging geany-themes project into the Geany tree,
as well as a few fixups to the Colorschemes menu, some of which are
same as patches sent to the mailing list some time ago. Mostly left is
cleaning up themes that cause warnings on geany verbose output and to
test
Am 28.04.2011 09:32, schrieb Matthew Brush:
On 04/28/11 00:01, Frank Lanitz wrote:
Hi,
Am 12.03.2011 19:11, schrieb Frank Lanitz:
During the last weeks a huge number mails at this list was stating to
make usage of GObject on building up a new plugin interface. It has been
talked about
Le 28/04/2011 01:49, Colomban Wendling a écrit :
Le 10/04/2011 15:03, Jiří Techet a écrit :
[...]
2edb068b81cb6d541d667efecd0ec4c346f0df51 Open the file in the
msgwindow even if no linenumber is specified
I'll review this one later (tomorrow if it goes right).
I don't really like the patch
Le 28/04/2011 02:06, Lex Trotman a écrit :
I understand that if your plugin makes use of some file patterns, it
then makes sense to show them in the FIF dialog. But Geany don't use
project patterns, and adding such patters to projects seems useless to
me since their only usage is to show them
On Thu, Apr 28, 2011 at 19:46, Colomban Wendling
lists@herbesfolles.org wrote:
Le 28/04/2011 01:49, Colomban Wendling a écrit :
Le 10/04/2011 15:03, Jiří Techet a écrit :
[...]
2edb068b81cb6d541d667efecd0ec4c346f0df51 Open the file in the
msgwindow even if no linenumber is specified
On Thu, Apr 28, 2011 at 19:52, Colomban Wendling
lists@herbesfolles.org wrote:
Le 28/04/2011 02:06, Lex Trotman a écrit :
I understand that if your plugin makes use of some file patterns, it
then makes sense to show them in the FIF dialog. But Geany don't use
project patterns, and adding
Hi Matthew,
you couldn't express my feelings better.
On Thu, Apr 28, 2011 at 07:01, Matthew Brush mbr...@codebrainz.ca wrote:
On 04/27/11 21:01, Lex Trotman wrote:
- No need to maintain changelog and authors files
Changelog and authors are still needed for tarballs, but maybe they
can be
Hi,
I just noticed the change[1] in wording of the set filetypes menu which
was something that had (slightly) bothered me before, since I personally
consider most of the scripting languages as programming languages as
well. I'm not sure that the word Compiled is the best choice though,
I missed the the commit[1] before the previous one I mentioned, which is
a pretty cool feature if it does what I think it does. Is this
documented yet or is still a work in progress? Is it meant to let the
user reorganize/rename the menu items in the Set Filetypes menu?
I notice the default
Hey Matthew,
[...]
I'm not sure that the word Compiled is the best choice though, since it's
kind of vague:
Is Vala a compiled language because it's compiled into C code?
Is Python *not* compiled because it's compiled into bytecode?
Is Java a compiled language?
Java is if you use GCJ,
13 matches
Mail list logo
