Devel October 2011

devel@lists.geany.org

24 participants
65 discussions

Geany-Plugins: A couple of compiler warnings
by Frank Lanitz 02 Oct '11

02 Oct '11

Hi folks, Sorry to be a pain in the ass but I'm still receiving a couple of compiler warnings when I'm compiling the geany-plugins at my AMD64 box. Can you please be so kind and have a look and double check, these warnings can be ignored or even better fixed? I will copy in the warnings I'm receiving on building with waf: ../debugger/src/dpaned.c: In function 'on_change_current_page': ../debugger/src/dpaned.c:264:32: warning: cast to pointer from integer of different size [-Wint-to-pointer-cast] ../debugger/src/dpaned.c: In function 'dpaned_set_tabbed': ../debugger/src/dpaned.c:432:35: warning: cast to pointer from integer of different size [-Wint-to-pointer-cast] [ 32/194] c: debugger/src/dconfig.c -> _build_/debugger/src/dconfig.c.1.o [ 32/194] c: debugger/src/breakpoints.c -> _build_/debugger/src/breakpoints.c.1.o ../debugger/src/dconfig.c: In function 'config_set_panel': ../debugger/src/dconfig.c:350:70: warning: cast from pointer to integer of different size [-Wpointer-to-int-cast] ../debugger/src/dconfig.c:361:84: warning: cast from pointer to integer of different size [-Wpointer-to-int-cast] ../debugger/src/dconfig.c:372:90: warning: cast from pointer to integer of different size [-Wpointer-to-int-cast] ../debugger/src/dconfig.c:383:91: warning: cast from pointer to integer of different size [-Wpointer-to-int-cast] [...] ../geanylua/glspi_init.c:276:0: warning: "isblank" redefined [enabled by default] /usr/include/ctype.h:186:0: note: this is the location of the previous definition [106/194] c: geanylua/glspi_dlg.c -> _build_/geanylua/glspi_dlg.c.2.o ../geanylua/glspi_app.c: In function 'glspi_xsel': ../geanylua/glspi_app.c:113:4: warning: passing argument 3 of 'lua_tolstring' from incompatible pointer type [enabled by default] /usr/include/lua5.1/lua.h:149:26: note: expected 'size_t *' but argument is of type 'guint *' ../geanylua/glspi_app.c: In function 'glspi_keygrab': ../geanylua/glspi_app.c:582:66: warning: cast from pointer to integer of different size [-Wpointer-to-int-cast] [108/194] c: geanylua/glspi_doc.c -> _build_/geanylua/glspi_doc.c.2.o [109/194] c: geanylua/glspi_kfile.c -> _build_/geanylua/glspi_kfile.c.2.o [109/194] c: geanylua/glspi_run.c -> _build_/geanylua/glspi_run.c.2.o [110/194] c: geanylua/glspi_sci.c -> _build_/geanylua/glspi_sci.c.2.o ../geanylua/glspi_sci.c: In function 'glspi_copy': ../geanylua/glspi_sci.c:470:72: warning: cast from pointer to integer of different size [-Wpointer-to-int-cast] Please feel free to get in touch with me for some further debugging. Cheers, Frank P.S. Please remember to run make check on developing as a number of these cause a warning also there. -- http://frank.uvena.de/en/

1 0

Reminder: String freeze for Geany-Plugins soon
by Frank Lanitz 02 Oct '11

02 Oct '11

Hi Devs, This is just a reminder that I will do the string freeze for the Geany-Plugins 0.21 very soon (Most likely tomorrow afternoon UTC). So please commit all changes on strings until tomorrow afternoon into trunk as I will create a release branch from it. Cheers, Frank -- http://frank.uvena.de/en/

1 0

Announcements (was: Re: [Geany] geany regexp replace)
by Enrico Tröger 02 Oct '11

02 Oct '11

On Sat, 1 Oct 2011 10:14:43 +1000, Lex wrote: >> [..thinking about finally announcing the wiki...] >> >> If nobody else has any blockers in mind, we could finally announce it >> to get more people look, use and extend it :). >> >> The only question is whether it is better to announce it before or >> after the release or together? >> > >By all means lets make it a *big* announcement. While thinking about announcements, we have right now (well, very soon at least) three announcements ready to be go out: - the wiki - the release - the changed project maintainer I'm just not yet completely sure in what order to get them into the world. Probably the wiki is a complete separat announcement, to be made on its own. Could be done easily and quickly. The other two might be combined, that is, in the usual release announcement include the hoorays for Colomban as the new project maintainer. What do you guys think? Regards, Enrico -- Get my GPG key from http://www.uvena.de/pub.asc

2 2

Re: [Geany-devel] Updated VCS info on the wiki
by joshua.rh＠comcast.net 02 Oct '11

02 Oct '11

Nice catch, I've updated the wiki. While I've started this thread; is there anything (specifically) anyone wants me to look into about either the VCS' or the hosting sites? I sort of just looked around their about pages, and tried to confirm some things I'd heard ----------------------------- Hi Josh, Only comment I'd make is that you only listed needing a login on Google, but AFAIK every other system also needs a login of some type, as does the current SVN so its not a discriminator. Cheers Lex

1 0

How about calling the next release 1.0?
by Jiří Techet 02 Oct '11

02 Oct '11

Hi, just one very quick and possibly stupid idea. How about getting rid of the 0 version prefix and calling the next release 1.0? This would be just numbering change, not some milestone based on features that have to be implemented (similarly to renumbering linux kernel from 2.6.x to 3.0). Rationale: the 0.xx versioning scheme makes an impression that Geany is something very unstable that crashes every five minutes and whose first release was made a few months back. Instead, Geany is a very stable and reliable editor with lots of features and several years of history. I know there are some 1.0 TODOs here: http://www.geany.org/Documentation/ToDo like the ABI stability for plugins and other features. But 1. Will the ABI be ever considered stable? Is it really needed? (All the plugins I know are open source and the combined plugin project is kept in sync with the development release so there's no real problem even if the API changes). 2. I think there's no need to require some specific features for the 1.0 release. The current set of features makes already a very good editor and extra features can always be introduced in later versions. I already find Geany more usable for my needs than editors having 2011 as their version number so I believe it deserves the 1 prefix. What is your opinion? Cheers, Jiri

14 26

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

Devel October 2011