Devel

devel@lists.geany.org

1641 discussions

Windows binaries for testing (was: Re: Geany 1.23 Waf install under win32)
by Enrico Tröger 13 Apr '14

13 Apr '14

On 11/04/14 20:04, Enrico Tröger wrote:> On 11/04/14 19:24, Enrico Tröger wrote: >> On 11/04/14 08:41, Steven VALSESIA wrote: >>> Hi ! >>> >>> I wanted to try this test-build >>> http://uvena.de/tmp/geany-1.24_setup_test.exe, but I cannot ran it. >>> I had to had these dependency : >>> >>> >>> *libgcc_s_sjlj-1.dlllibstdc++-6.dlllibwinpthread-1.dll* >>> >>> But even if I had them, I cannot run it because my version of >>> libstdc++-6.dll (and number of other I tested) don't have the call for >>> __gxx_personality_sj0. >>> >>> What's the problem ? (I'm running Windows 7 pro 64bits). >> >> Ouch. >> Not yet sure what's wrong, I'll have a look. >> I built the binaries also on Windows 7 64bits :(. > > Could you try the following Geany binary: > > http://uvena.de/tmp/geany_static.exe > > I built this one with -static but not really sure if it had any effect. > > Where is your libstdc++6.dll coming from? We don't ship it, so I'm > wondering. > > If the above binary won't work, could you then try to copy > http://uvena.de/tmp/libstdc%2b%2b-6.dll into the Geany bin directory, > next to geany.exe? This version is the one from the Strawberry Perl > distribution which includes a whole complete gcc build which I use to > compile the binaries. Forget the above, these files won't help. I built the binaries with a newly set up build environment on Windows 7, including much newer Mingw gcc bundle (previously 3.4, now 4.7). Either it was a change in gcc or a change in the updated Waf build system but now we need to pass -static-libgcc and -static-libstdc++ to the linker in order to remove the above noticed dependency. In the following builds I did this and tested them additionally on an old Windows XP (32bit): http://uvena.de/tmp/geany-1.24_setup_test2.exe http://uvena.de/tmp/geany-plugins-1.24_setup_test.exe Now, the installers and binaries included are also properly digitially signed by me in case anybody cares. I'd be happy if anyone else could test them and verify everything runs fine. Thanks. Regards, Enrico -- Get my GPG key from http://www.uvena.de/pub.asc

4 9

Setting Windows working directory
by Lex Trotman 10 Apr '14

10 Apr '14

Hi Enrico, We have had a report on IRC that running geany on the windows command line will only open files in the Geany install directory unless you use the full path. eg C:\somepath> geany somefile.txt will open installpath\somefile.txt not somepath\somefile.txt. And with the "Open new documents from the command line" option set it creates somefile.txt in the install dir since it doesn't exist there. Suspicion is falling on https://github.com/geany/geany/commit/775ef628688c69de34640e12666aed5762a80… As the most experienced windowser (and the committer of that change) could you look at it please? Cheers Lex

5 10

Geany bug hunting week
by Pavel Roschin 10 Apr '14

10 Apr '14

Hello! I tried to test Geany as much as possible to discover some issues before release. There are many bugs so I placed them into one big GitHub Gist. Summary: - autoclose plugin disabling segfault (maybe geany core) - geanylatex bug with symbol replace - manu interface issues (see Gist) - geanylatex at close segfault (see Gist for backtrace and IRC for investigation) - shift column plugin doesn't work at all (orphaned plugin, but invalid plugin in release isn't good) - GeanyPy/GeanyLua probably should list their plugins in the main plugin list (it's hard to use scripts). Also why not have python in core? Some design issues: - Adding plugin to Geany is very painful. Plugin creator should edit at least 14 (!!!) files spaghettized through whole project to do that. Also plugin creator should know two build systems (automake and waf). Possible solution - "onefile.c" plugin and "magic" command e.g. geany-make-plugin or geany-install-plugin. See GIMP for reference. - Lack of native scripting support. LuaJIT could be a _simple_ solution for that because of FFI interface and easy integration with C. Python also good but currently it's just plugin so not widely used. Also see GIMP plugin system for reference. One python script is enough to make plugin. - Plugins has MUCH copy-paste code: settings, help, keybindings. API simplification is possible I think. Creating simple wrappers will eliminate the GTK spaghetti. See full list and crash dumps here: https://gist.github.com/scriptum/9949771 -- Best regards, Pavel Roschin aka RPG

8 23

Geany-Plugins 1.24 string freeze
by Frank Lanitz 09 Apr '14

09 Apr '14

Hi translators and friends of Geany, We are on the final lap for a new release: 1.24 is near and will be release at the second weekend of April. As usual in prior we are having a phase to update the translations -- and here we are ;) I'd be very happy if you could send a patch, a pull request or single file with translation to either the geany-i18n mailing list or direct to me within the next two weeks so we can include it to the next release. Deadline will be 2014-04-12. To make it more easy for you I've already uploaded updated versions of the po files as well as to git master. You can either download the direct via web or by cloning the repository from https://github.com/geany/geany-plugins This can be done e.g. with git clone https://github.com/geany/geany-plugins.git Also at http://i18n.geany.org/plugins are statistics and daily updated files available (updated files by tomorrow CEST) As mentioned before, we are trying to have all translations complete by 2014-04-12. If your language was translated by two or more in past, please double check directly with them or by pinging me, so we don't need to translate same things two or three times. Also please feel to ping me for every question or if you like to start a new translation for an unsupported language. Thanks and happy translating Frank

1 2

Geany 1.24 string freeze
by Frank Lanitz 09 Apr '14

09 Apr '14

Hi translators and friends of Geany, As with the plugins, we are also on the final lap for a new release of Geany core: 1.24 is near and will be release at the second weekend of April. As usual in prior we are having a phase to update the translations -- and here we are again ;) I'd be very happy if you could send a patch, a pull request or single file with translation to either the geany-i18n mailing list or direct to me within the next two weeks so we can include it to the next release. Deadline will be 2014-04-12. To make it more easy for you I've already uploaded updated versions of the po files as well as to git master. You can either download the direct via web or by cloning the repository from https://github.com/geany/geany This can be done e.g. with git clone https://github.com/geany/geany.git Also at http://i18n.geany.org are statistics and daily updated files available (updated files by tomorrow CEST) As mentioned before, we are trying to have all translations complete by 2014-04-12. If your language was translated by two or more in past, please double check directly with them or by pinging me, so we don't need to translate same things two or three times. Also please feel to ping me for every question or if you like to start a new translation for an unsupported language. Thanks and happy translating Frank

1 2

Update of SSL certs
by Frank Lanitz 08 Apr '14

08 Apr '14

Hi folks, Due to the little security fluctuation on openssl geany.org will get a new SSL certificate soon. This will include changing the fingerprint as well as cycling the webserver. I will let you know ones everything is complete. Cheers, Frank

1 1

Geany Releases
by Lex Trotman 03 Apr '14

03 Apr '14

Since we are about to produce a new release I propose a change to the Geany workflow. More regular releases. Acknowledging that Geany hasn't the number of contributors that say firefox has, monthly would seem too often, so instead I propose an 8 week schedule: - week 4 feature freeze, alpha release for testing - week 6 string freeze, beta release for testing - week 7 release candidate - week 8 THE RELEASE!!! Then we don't need to be so careful about changes, because problems only last for a couple of months until the next release, and since only a few new features will be added each release nobody will feel that they have lost much if they have to downgrade due to bugs. I therefore propose that the eight week period should start today April 1. Happy upgrading. Cheers Lex

4 4

My PR isn't good ?
by Steven VALSESIA 31 Mar '14

31 Mar '14

Hi everybody ! I checked all my PR, didn't see any comment, but they're still not merged and i don't if there is a reason, or anything else. Can someone can check them ? :) I think it would be nice to merge the PR#224, since it already been a discussed PR ! I know the 2 other PR are maybe not good enough to be merged :) https://github.com/geany/geany/pull/224 https://github.com/geany/geany/pull/219 (make the string more accurate with PR 218) https://github.com/geany/geany/pull/218 (let the user choose between Windows or Gtk color chooser) Cheers, Steven Valsesia

5 8

Request to merge PR #226
by Shankhoneer Chakrovarty 29 Mar '14

29 Mar '14

Hi guys, I know everybody is busy with release of geany 1.24 . Can somebody please find sometime to merge PR#226<https://github.com/geany/geany/pull/226> so that it goes to geany release 1.24? If there is some problem please do tell me. I would fix it asap. Thanks, Shankhoneer Chakrovarty

2 4

Re: [Geany-Devel] Plugin-Maintainer: Please review PR and comment on them/merge them
by Matthew Brush 29 Mar '14

29 Mar '14

On 14-03-28 10:31 AM, Pavel Roschin wrote: >> >> >> Am 28.03.2014 10:00, schrieb Lex Trotman: >>> On 28 March 2014 19:46, Frank Lanitz <frank(a)frank.uvena.de> wrote: >>>> Am 28.03.2014 01:10, schrieb Lex Trotman: >>>>> The one you made on Geanypy has already been improved by upstream >>>>> (Matthew) so you should just commit that improvement. >>>> >>>> I was planning to have a look onto it Sunday (you mean #116, don't >>>> you?). But this is not a feature, only kind of a bug fix ;) >>> >>> Yep that one, I guess its more a feature since there is no bug (in >>> Geanypy), more its a bug in cppcheck :) >> >> >> ... well.... puh... At least it's not changing any string ;) >> However, will do it at the weekend. >> >> cheers, >> Frank >> _______________________________________________ >> Devel mailing list >> Devel(a)lists.geany.org >> https://lists.geany.org/cgi-bin/mailman/listinfo/devel > > > Here is definitely false-positeve. cppcheck was confused by a terrible define: > return operator inside... Without return operator of course here could be a bug. > Good static analyzer (eg. clang's static analyzer) can expand macros and would see the return. Maybe we could/should preprocess the code before we cppcheck it? IIRC Py_RETURN_NONE just expands to something like Py_INCREF(Py_None); return Py_None; I'm not opposed to using the full code like this, it's maybe a little nicer than the "fix" I mentioned in the PR comment, but IIRC there are multiple places where `Py_RETURN_NONE` and `Py_RETURN_TRUE/FALSE` are used like this that might also need to be updated. Cheers, Matthew Brush

2 1

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

Devel