Re: [Geany-devel] ANN: mailing list server move
Am 27.09.2012 22:40, schrieb Colomban Wendling:
Le 27/09/2012 22:36, Enrico Tröger a écrit :
On 27/09/12 21:59, Colomban Wendling wrote:
Le 27/09/2012 21:54, Enrico Tröger a écrit :
Hi all,
just as a note: I plan to move all Geany-related mailing lists from
uvena.de to the geany.org server on Friday, October 5 2012, around 12:00
UTC.
Great ! Just to be sure, current @uvena.de will be forwarded (at least
for some time) to the equivalent one at @geany.org I guess, right? :)
Yeah, that's the plan.
The list names will stay the same (only top level domain changes) except
for the main mailing list which is currently ge...@uvena.de. I guess
I'll rename it to geany-us...@geany.org which reads better than
ge...@geany.org.
Any objections?
Nope. Maybe I'd rather have used something like
{devel,users}@lists.geany.org but geany-{users,devel}@geany.org is fine too.
I'd also prefer lists.geany.org or something for host...
Cheers,
Frank
signature.asc
Description: OpenPGP digital signature
___
Geany-devel mailing list
Geany-devel@uvena.de
https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] Windows Build commands
On Tue, 28 Aug 2012 07:38:52 +1000 Lex Trotman ele...@gmail.com wrote: Hi Enrico or some other Windows dev, Had a report on IRC from a new Windows Geany user that when they installed Geany the C compile command was gcc -m32 “%f” -o “%e.exe” which didn't work, but when they pressed the reset in the build commands dialog the command changed to the normal gcc -Wall -o %e %f which worked. Is the build command being deliberately changed on windows builds or is it something picked up from the build environment accidently? And if it is deliberate, it doesn't seem to work? Are you referring to filetypes.c and the preconfigured command for compiling? If yes: This hasn't changed for 6 years according to blame and I don't know of any Windows-special-setup here. Cheers, Frank -- http://frank.uvena.de/en/ pgpKit4Gk4Xap.pgp Description: PGP signature ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] Geany-Plugins Dependency Consolidation
Am 06.08.2012 03:38, schrieb Lex Trotman: On 6 August 2012 05:35, Matthew Brush mbr...@codebrainz.ca wrote: On 12-08-05 07:57 AM, Frank Lanitz wrote: On Sun, 5 Aug 2012 16:55:07 +0200 Frank Lanitz fr...@frank.uvena.de wrote: For a list of the dependencies, you can look through the `build` directory's .m4 files and manually extract them (like I did for some of the shared ones previously). The ones with the highest versions will be the minimum version required to build geany-plugins (as a whole). Maybe building a script doing this would be a good idea. Having checked a couple of them I found it will be hard as they differ in way defining the dependencies... Yep and most don't specify their shared dependencies (GTK, GLIB, etc.) explicitly but assume that if you have the Geany, you have what they need. Agree with you that that is bad, they should be specified so that users can be sure that the plugin dev meant any version will do rather than that they just forgot to specify it :) ACK. Cheers, Frank ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] Geany-Plugins Dependency Consolidation
On Sun, 5 Aug 2012 10:21:04 +1000 Lex Trotman ele...@gmail.com wrote: On 5 August 2012 03:40, Matthew Brush mbr...@codebrainz.ca wrote: On 12-08-04 09:41 AM, Colomban Wendling wrote: [...] So... maybe I got your point wrong, but I don't think it's any kind of a problem to have different dependencies from one plugin to another -- actually, I think each plugin should set it dependencies to exactly what it needs: nothing less (of course), and nothing more. You got it mostly. I just mean some way for the build system to handle multiple plugins sharing same dependencies like having webkit.m4 that enables/disables multiple plugins if not found. So when you configure, it says something like this: checking for WebKit = x.xx ... no Disabling plugins: WebHelper, Devhelp, Markdown I don't see this, the *plugin* should define what it needs, not some arbitrary external build script. My (limited) understanding of the plugin autofoo is that is how its done now by having local build scripts in each plugin. If they require different versions that might mean you get Webhelper and Devhelp but not Markdown, but your scheme won't allow that. So if the Markdown dev added some new feature that needed a higher version I can't build the other two unless I upgrade my system :( We should not be forcing the *highest* version needed by plugins. I agree. But I also see the point of consolidation of dependencies. Its getting really complicated to say geany-plugins needs this dependencies, but I think its an issue we need to solve on social level, not trying to solve it with some hack. Is there any chance to get a complete list which plugins depend on which library out of autotools? Cheers, Frank -- http://frank.uvena.de/en/ pgpl6kSkojQ91.pgp Description: PGP signature ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] Geany-Plugins Dependency Consolidation
On Sun, 5 Aug 2012 22:24:12 +1000 Lex Trotman ele...@gmail.com wrote: On 5 August 2012 21:47, Frank Lanitz fr...@frank.uvena.de wrote: On Sun, 5 Aug 2012 10:21:04 +1000 Lex Trotman ele...@gmail.com wrote: On 5 August 2012 03:40, Matthew Brush mbr...@codebrainz.ca wrote: On 12-08-04 09:41 AM, Colomban Wendling wrote: [...] So... maybe I got your point wrong, but I don't think it's any kind of a problem to have different dependencies from one plugin to another -- actually, I think each plugin should set it dependencies to exactly what it needs: nothing less (of course), and nothing more. You got it mostly. I just mean some way for the build system to handle multiple plugins sharing same dependencies like having webkit.m4 that enables/disables multiple plugins if not found. So when you configure, it says something like this: checking for WebKit = x.xx ... no Disabling plugins: WebHelper, Devhelp, Markdown I don't see this, the *plugin* should define what it needs, not some arbitrary external build script. My (limited) understanding of the plugin autofoo is that is how its done now by having local build scripts in each plugin. If they require different versions that might mean you get Webhelper and Devhelp but not Markdown, but your scheme won't allow that. So if the Markdown dev added some new feature that needed a higher version I can't build the other two unless I upgrade my system :( We should not be forcing the *highest* version needed by plugins. I agree. But I also see the point of consolidation of dependencies. Its getting really complicated to say geany-plugins needs this dependencies, Well, I am not sure that we should be saying geany-plugins has dependencies anyway. IIUC, at least Debian packages each plugin separately anyway. I can't speak for other distros but it makes sense for users to be able to get just the plugins they want. Building the whole lot from source or git is fine, plugins that don't have their needs met don't build, but do tell you about it. but I think its an issue we need to solve on social level, not trying So I agree with Colomban, that there isn't anything to solve, different plugins have different dependencies, thats life. My goal is not to synchronize dependencies with a sword in my hand. I'm thinking about having a single point where the self-compiling use is able to check which version is needed for which plugin. So maybe an extension of Matthew's list inside a global INSTALL/README/whatever Cheers, Frank -- http://frank.uvena.de/en/ pgpoHC8kVoq1y.pgp Description: PGP signature ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] Geany-Plugins Dependency Consolidation
On Sun, 05 Aug 2012 05:27:08 -0700 Matthew Brush mbr...@codebrainz.ca wrote: On 12-08-05 04:47 AM, Frank Lanitz wrote: On Sun, 5 Aug 2012 10:21:04 +1000 Lex Trotman ele...@gmail.com wrote: On 5 August 2012 03:40, Matthew Brush mbr...@codebrainz.ca wrote: On 12-08-04 09:41 AM, Colomban Wendling wrote: [...] So... maybe I got your point wrong, but I don't think it's any kind of a problem to have different dependencies from one plugin to another -- actually, I think each plugin should set it dependencies to exactly what it needs: nothing less (of course), and nothing more. You got it mostly. I just mean some way for the build system to handle multiple plugins sharing same dependencies like having webkit.m4 that enables/disables multiple plugins if not found. So when you configure, it says something like this: checking for WebKit = x.xx ... no Disabling plugins: WebHelper, Devhelp, Markdown I don't see this, the *plugin* should define what it needs, not some arbitrary external build script. My (limited) understanding of the plugin autofoo is that is how its done now by having local build scripts in each plugin. Yeah, and currently the plugins each check for the same shared dependencies, but it doesn't show what they're checking for, it just shows the plugin's name, like: checking for DEVHELP ... no What I'm asking about is to have a webkit.m4 (for example) or something that the plugins which use that dependency can make use of and so the check is only done once and if not found, it ouputs as I said previously. Of course I don't know if it's realistic/feasible, which is why I was asking. Sounds like a great idea. I support this wish. If they require different versions that might mean you get Webhelper and Devhelp but not Markdown, but your scheme won't allow that. So if the Markdown dev added some new feature that needed a higher version I can't build the other two unless I upgrade my system :( I mean they should require the same version, the same *lowest* version they can work with (even if they need some minor changes to make it possible). Should but not have to. I agree. We should not be forcing the *highest* version needed by plugins. Not what I meant. But it's sort of what we do now if you consider building geany-plugins as a whole. I agree. But I also see the point of consolidation of dependencies. Its getting really complicated to say geany-plugins needs this dependencies, but I think its an issue we need to solve on social level, not trying to solve it with some hack. Is there any chance to get a complete list which plugins depend on which library out of autotools? What I was asking about wouldn't be a hack, it would just be to change the plugins a bit so they depend on the same version of shared libraries, and then to have Autotools do a check for the shared dependency. Yes. It's mainly not a technical issue. Just some social issue where developers/maintainer have to talk to each other. For a list of the dependencies, you can look through the `build` directory's .m4 files and manually extract them (like I did for some of the shared ones previously). The ones with the highest versions will be the minimum version required to build geany-plugins (as a whole). Maybe building a script doing this would be a good idea. Cheers, Frank -- http://frank.uvena.de/en/ pgpE6ivcX38J3.pgp Description: PGP signature ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] Geany-Plugins Dependency Consolidation
On Sun, 5 Aug 2012 16:55:07 +0200 Frank Lanitz fr...@frank.uvena.de wrote: For a list of the dependencies, you can look through the `build` directory's .m4 files and manually extract them (like I did for some of the shared ones previously). The ones with the highest versions will be the minimum version required to build geany-plugins (as a whole). Maybe building a script doing this would be a good idea. Having checked a couple of them I found it will be hard as they differ in way defining the dependencies... Cheers, Frank -- http://frank.uvena.de/en/ pgpgBdRN36CpM.pgp Description: PGP signature ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] Dropping Waf support?
Am 16.07.2012 19:36, schrieb Enrico Tröger: Hey all, this topic has been brought up already a couple of times, for example on [1]. What do you think about dropping Waf support in Geany and in the Geany-Plugins project? While I was defending Waf in Geany, I somewhat changed my mind. Not because I don't like it anymore, but I increasingly see the efforts in maintaining two (to be exactly three for Geany) build systems is too much. Since the make/MSYS build system support seems to get better and better due to Nick's and Dimitar's work on it, I thought about dropping the Waf support. It seems nobody knows it well enough and probably except for a few users nobody is using it. (And obviously I don't do so much anymore and also lost a bit interest in maintaining forever.) The other thing is that Waf causes often problems for distro packages, especially for the Debian folks [2]. So, I'd go the easy way in this case and just remove Waf. Then we only need to maintain the autotools based build system for non-Windows systems and the make based for Windows. For Geany-Plugins, we would need to get something working on Windows but maybe we could re-use Geany's make based system for Windows here. What do you guys think? As long as I don't need to maintain autotools I'm fine with every solution I just never understood how it really works even I tried a couple of times. ;) However: One good maintained system is better than 2 doing different things. Cheers, Frank ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] Third party plugin publish and third party library bundle problem
On Mon, 16 Jul 2012 16:59:12 +0200 Thomas Martitz thomas.mart...@student.htw-berlin.de wrote: Am 16.07.2012 16:58, schrieb Thomas Martitz: Am 16.07.2012 16:41, schrieb Hong Xu: On 2012/7/15 20:28, Frank Lanitz wrote: On Sun, 15 Jul 2012 21:56:32 +1000 Lex Trotman ele...@gmail.com wrote: BTW you mentioned a third party library, but you didn't say what library. It would of course have to have a suitable license to allow it to be included. Yes. I missed that too. Most plugins are GPL2+ so it needs to be also GPL2+... BSD should also be fine in most cases. But LGPL could be problematic. I prefer Simplified BSD License for this plugin. What do you mean it should be fine for most cases? Could you explain more? The 2-clause BSD is always fun. As is LGPLv2+. s/fun/fine/ :) Rethinking about . well, you might are correct. In terms of distribution as we most likely will do, LPGL should also be fine. Sorry - my fault. In terms of BSD I'm thinking about some special parts e.g. calling author's names inside credits I saw in past. But should not be apply able on our case Cheers, Frank -- http://frank.uvena.de/en/ pgpXZbmoQPcMW.pgp Description: PGP signature ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] Third party plugin publish and third party library bundle problem
On Mon, 16 Jul 2012 23:13:55 +0800 Hong Xu d...@hong.me wrote: On 2012/7/15 15:49, Frank Lanitz wrote: On Sat, 07 Jul 2012 13:39:56 +0800 Hong Xu d...@hong.me wrote: Whatever the answer is, can I put my plugin in https://github.com/geany/geany-plugins ? This repository seems better maintained than mine. I didn't have a look onto you code by now but in general you can add you plugin also to geany-plugins project. I'd prefer you to having you own fork of plugins and sending pull request against geany/geany-plguins/master The second problem is that, how should I bundle a third party C library with my plugin? I think Matthew answered here very well. It really depends on how common this library is or if you are patching it in some kind. Well... I don't like shipping to much libraries with one plugin as there is always an question of updates in terms of a security fault etc. Also this might could cause ending up in typical Windows scenario where you are might having GTK installed about 1000 times - each GTK serving its own application. So: if the library is typical packaged for target platforms or if its available via a common way (e.g. ppa on Ubuntu, some of the rpm-pages for SuSE or Fedora/RH/SL) and you don't have any patches inside I wouldn't deliver it with the plugin but depend on it. Currently, the library is not commonly distributed under common distributions. The library URL is: https://github.com/editorconfig/editorconfig-core Based on that I think including would be fine. There's a problem here: the library build system is based on CMake, while the geany-plugins project supports both autotools and waf. If I want to include the source in my code, I would probably have to reproduce the cmake build system using autotools. Do you have any suggestions handling a CMake third party library in geany-plugins? And do I also need to support BOTH the two build systems? Well please include it to autotools if ever possible. Even cmake might have some advantages (cannot say) I don't see any chance in terms of man power etc to have it also maintained. Cheers, Frank -- http://frank.uvena.de/en/ pgpR64oy5iLaV.pgp Description: PGP signature ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] Introduction
On Fri, 13 Jul 2012 16:27:35 -0700 Sean Felipe Wolfe ether@gmail.com wrote: Hey Jacob ... my name is Sean Wolfe and I'm in a similar position to yourself, not a lot of Geany type contributions made as yet but I'm enthusiastic about the technology and would like to see it grow. I just got back on the Geany list after some time away from Geany , and I saw your intro hadn't been responded to so just wanted to say hi. A bit late but just to reassure you you aren't the only interested party :) Great to here! Its always great to to have contributions of coding power ;) (As Lex mentioned, a good starting point is reading HACKING and making a fork of geany git repository followed by reading code, messing around etc;) ) Cheers, Frank -- http://frank.uvena.de/en/ pgp2e3XKdJhYj.pgp Description: PGP signature ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] Third party plugin publish and third party library bundle problem
On Sat, 07 Jul 2012 13:39:56 +0800 Hong Xu d...@hong.me wrote: Whatever the answer is, can I put my plugin in https://github.com/geany/geany-plugins ? This repository seems better maintained than mine. I didn't have a look onto you code by now but in general you can add you plugin also to geany-plugins project. I'd prefer you to having you own fork of plugins and sending pull request against geany/geany-plguins/master The second problem is that, how should I bundle a third party C library with my plugin? I think Matthew answered here very well. It really depends on how common this library is or if you are patching it in some kind. Well... I don't like shipping to much libraries with one plugin as there is always an question of updates in terms of a security fault etc. Also this might could cause ending up in typical Windows scenario where you are might having GTK installed about 1000 times - each GTK serving its own application. So: if the library is typical packaged for target platforms or if its available via a common way (e.g. ppa on Ubuntu, some of the rpm-pages for SuSE or Fedora/RH/SL) and you don't have any patches inside I wouldn't deliver it with the plugin but depend on it. Cheers, Frank -- http://frank.uvena.de/en/ pgp4WMnbkcOwC.pgp Description: PGP signature ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] Third party plugin publish and third party library bundle problem
On Sun, 15 Jul 2012 21:56:32 +1000 Lex Trotman ele...@gmail.com wrote: BTW you mentioned a third party library, but you didn't say what library. It would of course have to have a suitable license to allow it to be included. Yes. I missed that too. Most plugins are GPL2+ so it needs to be also GPL2+... BSD should also be fine in most cases. But LGPL could be problematic. -- http://frank.uvena.de/en/ pgpEfyn4bOLCy.pgp Description: PGP signature ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] [Geany] ANN: Geany-Plugins 1.22 released!
Hi, Am 11.07.2012 20:31, schrieb Frank Lanitz: Windows builds are not done by now, but will be uploaded to the download peges soon. Windows builds have been also uploaded and can be downloaded from http://plugins.geany.org/downloads.html If you like to verify your download the PGP-signiture is also available via this page. Have fun! Cheers, Frank ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
[Geany-devel] ANN: Geany-Plugins 1.22 released!
Hi all, We are happy to announce the release of Geany Plugins 1.22 which is targeted to work with Geany 1.22. As major changes, two new plugins and one old plugin -- GeanyMiniScript, GeniusPaste, MultiTerm -- has been added to geany-plugins whereas default build of GeanyGDB with autotools has been deactivated. As usual, tarballs and their corresponding GPG signatures can be found at http://plugins.geany.org/downloads.html. Windows builds are not done by now, but will be uploaded to the download peges soon. A comprehensive list of changes can be found at http://plugins.geany.org/geany-plugins/geany-plugins-1.22.NEWS. Cheers, Frank signature.asc Description: OpenPGP digital signature ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] Treebrowser patch
Am 06.07.2012 09:32, schrieb Lex Trotman: On 6 July 2012 16:02, Frank Lanitz fr...@frank.uvena.de wrote: Am 06.07.2012 03:39, schrieb Lex Trotman: Frank, Colomban, Since you seem to have adopted treebrowser by the latest commits :) I've just done some C89/90 related changes. ... Tz tz tz. ;) Heh, by naming the most prolific recent committers I was hoping that one of them would ensure that the simple patch made it in before the release, after all having a preference that can be set in several ways but is never tested anywhere is kinda fundamental :) I will try to have a look and run some tests tonight. Cheers, Frank ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
[Geany-devel] Geany-Plugins: String freeze for 1.22 release
Hi translators and friends of Geany, After 1.22 release of Geany we are on final road to release also Geany-Plugins 1.22. The list of changes done for this release is long and so a lot of string have changed or were added. I like to ask all translators to check the translations. 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 2012-07-07. To make it more easy for you I've already uploaded updated versions of the po files (and now this is new) to git master as well as 1.22_release-branch at github. 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. As mentioned before, we are trying to have all translations complete by 2012-07-07. 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 signature.asc Description: OpenPGP digital signature ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
[Geany-devel] Plugin-Maintainer: Please do you final changes on strings - String freeze soon
Hi plugin developers, Please be so kind and submit your last changes for 1.22 release of plugins until Wednesday noon CEST as after this I want to do the string freeze. During this string freeze I will create a 1.22-release-branch where we only merge fixes and improvements e.g. for documentation and of course translation updates. So if you are doing a major feature enhancement this can still go to master after - keep this in mind on creating the pull requests etc. However, release of Geany-Plguins 1.22 is currently planned for about 1st weekend in July. Cheers, Frank -- http://frank.uvena.de/en/ pgpV34vzo2x0t.pgp Description: PGP signature ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
[Geany-devel] Plugins-developers: Please update you README-files
Hi folks, And another request in preparation of upcoming 1.22 release of Geany-Plugins: Please update your README-files. There are a number of plugins where you still can find such information like this: Installation Compiling and installing the code is done by the following three commands:: $ ./configure $ make $ make install For more configuration details run:: $ ./configure --help Even that might be true, geany-plugins are intended to being compiled from / folder, not from single plugin folder, so inside each plugins README there should only be a reference to global building instructions. Cheers, Frank ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
[Geany-devel] Plugins-developers: Please check bugs on sourceforge
Hey plugin developers, There are a number of bugs still open on sourceforge [1]. Can you please be so kind and check for your plugins (or maybe other plugins as you like) whether you can reproduce the bug, can provide any help or just fixing it? Would be cool if we could close some more until upcoming release. Cheers, Frank [1] http://sourceforge.net/tracker/?group_id=222729atid=1056532 ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
[Geany-devel] Plugins-maintainers: Please update Maintainers-file
Hi plugin-developers, There are still a lot of plugins which don't have complete information at MAINTAINERS-file of geany-plugins [1]. Please be so kind and update it with latest information so we got up to date information when release geany-plugins in about 3 weeks from now. Cheers, Frank [1] https://github.com/geany/geany-plugins/blob/master/MAINTAINERS -- http://frank.uvena.de/en/ pgpSVJh2AqeMW.pgp Description: PGP signature ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
[Geany-devel] String freeze for Geany 1.22
Hi translators and friends of Geany, Time is passing by and it's time for doing a new release of Geany! To manage all translation coming in in time we are having a string freeze for upcoming Geany 1.22, which will be release around June, 18th. The list of changes done for this release is long and so a lot of string have changed or were added. I like to ask all translators to check the translations. 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 2012-06-15. To make it more easy for you I've already uploaded updated versions of the po files (and now this is new) to git master at github. 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. As mentioned before, we are trying to have all translations complete by 2012-06-15. 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 P.S. As we are used to on previous releases also the combined geany-plugins project will have a new stable release. Its currently scheduled two weeks after Geany 1.22 with a string freeze around release date of Geany. If you like to provide also some translation for, it would be much appreciated. ;) -- http://frank.uvena.de/en/ pgpcToXUSS4a8.pgp Description: PGP signature ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] Geany Newsletter Issue #5
Am 28.05.2012 13:27, schrieb Lex Trotman: On 28 May 2012 19:59, Thomas Martitz thomas.mart...@student.htw-berlin.de wrote: Am 28.05.2012 11:27, schrieb Frank Lanitz: It's important to note that the dynamic library loading mechanism that loads plugins is C functionality and does not know about C++ constructors. This means that global and static objects in the plugin will *not* have their constructors called when the plugin is loaded. Use dynamically created objects as show in the above example. I'm not sure this is true. libdl should handle this (i.e. call functions point to in the init and fini sections). |__attribute__ ((constructor)) and||__attribute__ ((destructor)) is supported works with as well. This doesn't actually call the C++ constructors/destructors in the way they would be in normally be if the plugin had been statically linked. This simply labels a C function to be called at dlopen time. It may be used to do some initialisation, but you would have to manually call each constructor, ... too error prone, Franks advice to create everything dynamically is sound. It's not mine, as I really don't have a clue about this section. Content was introduced by a patch IIRC by Matthew and you ;) Cheers, Frank signature.asc Description: OpenPGP digital signature ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] geany-plugins: Bleeding-edge compatibility
On Thu, 19 Apr 2012 17:38:00 +0200 Quentin Glidic sardemff7+ge...@sardemff7.net wrote: On 19/04/2012 16:43, Matthew Brush wrote: An explanation would be useful. For MultiTerm, presumably it's to avoid a clash with GLib.Menu/MenuItem? Is GIO stuff part of the implicit namespace for GLib? Yes, and yes. If the answer to those is yes, it looks fine to apply as is. Even if the answer is no, the patch shouldn't harm anything besides cluttering up the code a little bit. Attached a new patch with a better commit message. I'm afraid its not applying. Can you rebuild it for current head? Cheers, Frank -- http://frank.uvena.de/en/ pgpl2SqtgoRPc.pgp Description: PGP signature ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] geany-plugins: Bleeding-edge compatibility
Am 10.05.2012 02:20, schrieb Matthew Brush: On 12-05-09 01:02 PM, Frank Lanitz wrote: On Thu, 19 Apr 2012 17:38:00 +0200 Quentin Glidicsardemff7+ge...@sardemff7.net wrote: On 19/04/2012 16:43, Matthew Brush wrote: An explanation would be useful. For MultiTerm, presumably it's to avoid a clash with GLib.Menu/MenuItem? Is GIO stuff part of the implicit namespace for GLib? Yes, and yes. If the answer to those is yes, it looks fine to apply as is. Even if the answer is no, the patch shouldn't harm anything besides cluttering up the code a little bit. Attached a new patch with a better commit message. With a view onto http://lists.uvena.de/pipermail/geany-devel/2012-May/006824.html Is this fine to append? Yeah it's fine. OK. will add it then later this week - I hope I find some time by today CEST but cannot give any guarantee. Cheers, Frank ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] geany-plugins: Bleeding-edge compatibility
On Thu, 19 Apr 2012 17:38:00 +0200 Quentin Glidic sardemff7+ge...@sardemff7.net wrote: On 19/04/2012 16:43, Matthew Brush wrote: An explanation would be useful. For MultiTerm, presumably it's to avoid a clash with GLib.Menu/MenuItem? Is GIO stuff part of the implicit namespace for GLib? Yes, and yes. If the answer to those is yes, it looks fine to apply as is. Even if the answer is no, the patch shouldn't harm anything besides cluttering up the code a little bit. Attached a new patch with a better commit message. With a view onto http://lists.uvena.de/pipermail/geany-devel/2012-May/006824.html Is this fine to append? Cheers, Frank -- http://frank.uvena.de/en/ pgpDJpMTMQyWZ.pgp Description: PGP signature ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] plugin data / html doc directories?
Am 05.05.2012 20:08, schrieb Dimitar Zhekov: BTW, the description of plugin_help() refers to utils_start_browser(), but the function name is utils_open_browser(). Fixed in git. Thx. signature.asc Description: OpenPGP digital signature ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] GeniusPaste, new plugin
On Sat, 28 Apr 2012 18:14:33 +0200 Enrico enrico@gmail.com wrote: If you consider this plugin interesting enough, I'd like to know what should I do to make it part of the Geany-Plugins project. I think it can be useful to have it inside the geany-plugins project. If you like to, just clone the geany-plugins project on github [1] and add you plugin into its structure and resend a pull request to the project. You can have a look onto other plugins if its about adding build support for waf and autotools - both are much appreciated. But if one of them is missing, there might somebody who will add it for you ;) Cheers, Frank [1] https://github.com/geany/geany-plugins -- http://frank.uvena.de/en/ pgpoqGrZ8AyZg.pgp Description: PGP signature ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] geany-plugins: Bleeding-edge compatibility
Am 16.04.2012 13:33, schrieb Quentin Glidic: Hello, Two minor compatibility patches to keep-up with bleeding-edge stuff. Dear Maintainer of Debugger and Multiterm Can you have a look at this patches and send pull request to geany-plugins master? Cheers, Frank ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] Wrap words Addon patch
Am 21.03.2012 00:33, schrieb Colomban Wendling: Le 20/03/2012 22:14, Frank Lanitz a écrit : On Tue, 13 Dec 2011 17:46:47 +0800 Nathan Broadbent nathan@gmail.com wrote: 1. Visit https://github.com/pzoxiuv/geany-plugins-1 2. Click 'Pull Request' 3. In the box on the right, you will see the heading 'Head branch · tag · commit'. There is an input field next to pzoxiuv/geany... @, where you should type your branch (addons_wraptext). 4. You can enter a title description, and double check the commits and changes. If everything looks good, click 'Send pull request' I guess you were answering to my Wrap Word Addon patches mail? Once this is done and Nathan is happy with your code he will send the pull request to geany-plugins and most likely I will have tons of comments but finally will add it ;) Hum huh heh heuu… what? You mean I create a pull request on geany/gneay-plugins right? I don't know who's Nathan actually, but I doubt he's the new addons maintainer -- or I missed some mails hard and I misread the MAINTAINERS file. Nathan build the original patch set introducing wrap word into addons plugin. Anyway, I created a pull request on the GP repo directly, hopefully it's what you meant and everything's fine. Its fine. Cheers, Frank ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] Wrap words Addon patch
Am 21.03.2012 15:14, schrieb Colomban Wendling: Le 21/03/2012 08:21, Frank Lanitz a écrit : Am 21.03.2012 00:33, schrieb Colomban Wendling: Le 20/03/2012 22:14, Frank Lanitz a écrit : On Tue, 13 Dec 2011 17:46:47 +0800 Nathan Broadbent nathan@gmail.com wrote: 1. Visit https://github.com/pzoxiuv/geany-plugins-1 2. Click 'Pull Request' 3. In the box on the right, you will see the heading 'Head branch · tag · commit'. There is an input field next to pzoxiuv/geany... @, where you should type your branch (addons_wraptext). 4. You can enter a title description, and double check the commits and changes. If everything looks good, click 'Send pull request' I guess you were answering to my Wrap Word Addon patches mail? Once this is done and Nathan is happy with your code he will send the pull request to geany-plugins and most likely I will have tons of comments but finally will add it ;) Hum huh heh heuu… what? You mean I create a pull request on geany/gneay-plugins right? I don't know who's Nathan actually, but I doubt he's the new addons maintainer -- or I missed some mails hard and I misread the MAINTAINERS file. Nathan build the original patch set introducing wrap word into addons plugin. If I read the mails and the blame correctly, it looks to me it was Alex Meyer :) Oh yepp. You are right. Sorry for blaming the wrong guy. ;) Cheers, Frank ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] Wrap words Addon patch
On Wed, 21 Mar 2012 15:31:50 +0100 Frank Lanitz fr...@frank.uvena.de wrote: Am 21.03.2012 15:14, schrieb Colomban Wendling: Le 21/03/2012 08:21, Frank Lanitz a écrit : Am 21.03.2012 00:33, schrieb Colomban Wendling: Le 20/03/2012 22:14, Frank Lanitz a écrit : On Tue, 13 Dec 2011 17:46:47 +0800 Nathan Broadbent nathan@gmail.com wrote: 1. Visit https://github.com/pzoxiuv/geany-plugins-1 2. Click 'Pull Request' 3. In the box on the right, you will see the heading 'Head branch · tag · commit'. There is an input field next to pzoxiuv/geany... @, where you should type your branch (addons_wraptext). 4. You can enter a title description, and double check the commits and changes. If everything looks good, click 'Send pull request' I guess you were answering to my Wrap Word Addon patches mail? Once this is done and Nathan is happy with your code he will send the pull request to geany-plugins and most likely I will have tons of comments but finally will add it ;) Hum huh heh heuu… what? You mean I create a pull request on geany/gneay-plugins right? I don't know who's Nathan actually, but I doubt he's the new addons maintainer -- or I missed some mails hard and I misread the MAINTAINERS file. Nathan build the original patch set introducing wrap word into addons plugin. If I read the mails and the blame correctly, it looks to me it was Alex Meyer :) Oh yepp. You are right. Sorry for blaming the wrong guy. ;) And now I recognized that I messed up whole thread. OMFG -- http://frank.uvena.de/en/ pgpW8m1vGT8yB.pgp Description: PGP signature ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] Wrap words Addon patch
On Tue, 13 Dec 2011 17:46:47 +0800 Nathan Broadbent nathan@gmail.com wrote: 1. Visit https://github.com/pzoxiuv/geany-plugins-1 2. Click 'Pull Request' 3. In the box on the right, you will see the heading 'Head branch · tag · commit'. There is an input field next to pzoxiuv/geany... @, where you should type your branch (addons_wraptext). 4. You can enter a title description, and double check the commits and changes. If everything looks good, click 'Send pull request' Once this is done and Nathan is happy with your code he will send the pull request to geany-plugins and most likely I will have tons of comments but finally will add it ;) Cheers, Frank -- http://frank.uvena.de/en/ pgpfl84JWcwe5.pgp Description: PGP signature ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] Usage of plugin_help()
Am 12.03.2012 00:24, schrieb Lex Trotman: [...] Question is, what do we really want to have behind that function? The delivery format is less important than actually providing help. I guess that's set. But how would such a thing look like? Well, since you are trying to get GP plugins to provide a ReST formatted readme why not make it a recommendation for a ReST formatted help which the GP build script can turn into an installed html file. So the plugin_help() just needs to call utils_open_browser(). Use the same css as Geany's manual and get a consistent look and feel. As to content, first guess recommended layout: How to use -- What it does, menu items, keybindings Preferences --- blah How to configure -- blah The last is only needed if there is configuration beyond the preferences settings. I like that idea. Cheers, Frank ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] Markers
Am 11.03.2012 07:16, schrieb Alexander Petukhov: So all we need is the initialisation, and probably a common search routine for the convenience of plugins (although that isn't absolutely needed). The smaller the patch the more likely someone has time to test it and commit it. I would vote for having utility functions that manages a list of available markers instead of letting plugins manually find those that are marked with SC_MARK_AVAILABLE. I can imagine a situation when some plugin set its markers for several documents but didn't do it for others, so when another plugin tries to set it's own markers it came to that markers idenifiers for the same markers are different in different documents that means it's another job to keep track of it. having such functions as utils_ui_get_marker(), utils_ui_free_marker() seems more clear and robust. I agree. Not because I really expect this going to happen very often, but because of it sounds like a cleaner solution for me with a defined API for plugin codes. Cheers, Frank signature.asc Description: OpenPGP digital signature ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
[Geany-devel] Usage of plugin_help()
Hi folks, I want to discuss shortly the expected behavior of plugin_help()-function implemented by plugins. Inside API-documentation its written: Called whenever the plugin should show its documentation (if any). This may open a dialog, a browser with a website or a local installed HTML help file(see utils_start_browser()) or something else. Can be omitted when not needed. Well... which means its not really defined what the user will expect once he push the button. Therefore we do have at least 2.5 major behaviors: - Geany is calling a browser and opening a webpage with info (spellcheck plugin) - Its opening a message window with * a short info about plugin (e.g. geanyLaTeX) * a long help text about plugin (e.g. geanymacro) Question is, what do we really want to have behind that function? Cheers, Frank signature.asc Description: OpenPGP digital signature ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] Commit messages on merges
On Sun, 04 Mar 2012 03:40:29 +0100 Colomban Wendling lists@herbesfolles.org wrote: IMO we should not record merges when there is only one single commit or when the commits are unrelated (though the latter should probably be less common) and rather rebase or cherry-pick the commits. However, we must keep the merge when the commits are a whole thing not to lose that information (when several commits are needed to implement a single thing). I agree. And in second case we have to keep care that merge message is informative enough to don't go into complete tree just to understand what have been done there. Personally I started using the git merge command from command line more often instead of github's web interface as its not satisfying my understanding. Cheers, Frank -- http://frank.uvena.de/en/ pgpWctMCRO6nv.pgp Description: PGP signature ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] Commit messages on merges
On Sat, 03 Mar 2012 18:57:34 -0800 Matthew Brush mbr...@codebrainz.ca wrote: On 12-03-03 06:28 PM, Colomban Wendling wrote: Le 04/03/2012 02:01, Jiří Techet a écrit : On Mon, Feb 27, 2012 at 08:33, Matthew Brushmbr...@codebrainz.ca wrote: On 12-02-26 11:20 PM, Frank Lanitz wrote: Hi folks, Just something I thought on last merges based on Jiri's patches. Its hard to understand what this merges do just by reading the commit message. Given, that we want to create the ChangeLog based on git log it will be nearly impossible to create a good ChangeLog/Newsfile if we don't keep care. Not sure how, but can we be more verbose here? [snip] Just to give everyone who hasn't checked the commits an idea of the verbosity that those commit messages has. Is it too verbose? I was trying to add some more detailed info because from my experience even though the patch seems to be clear now, when looking at it one year later I often feel like what does the hell the patch do? and why did I write something like that?. But if it's the preferred way I can move the explanation into the merge comment on github. Nope, it's fine IMO -- and I think Matthew quoted them just to tell Frank that despite the unclear merge message the commits themselves were well explained. Correct, they had some *really* good commit messages. The only problem was with my default merge messages I think. Yes. Message like --- Merged from foo/baa Fixes --- are not very useful. (Just a very pointed example to point it out) Cheers, Frank -- http://frank.uvena.de/en/ pgp8KglRL6feb.pgp Description: PGP signature ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] Commit messages on merges
On Sun, 04 Mar 2012 13:01:27 -0800 Matthew Brush mbr...@codebrainz.ca wrote: On 12-03-04 07:07 AM, Colomban Wendling wrote: Le 04/03/2012 09:28, Frank Lanitz a écrit : On Sun, 04 Mar 2012 03:40:29 +0100 Colomban Wendlinglists@herbesfolles.org wrote: IMO we should not record merges when there is only one single commit or when the commits are unrelated (though the latter should probably be less common) and rather rebase or cherry-pick the commits. However, we must keep the merge when the commits are a whole thing not to lose that information (when several commits are needed to implement a single thing). I agree. And in second case we have to keep care that merge message is informative enough to don't go into complete tree just to understand what have been done there. Personally I started using the git merge command from command line more often instead of github's web interface as its not satisfying my understanding. Same for me, moreover because I prefer to test the PR locally as a simple branch before doing the merge, so it's not much effort than using the GitHub UI, and it's a lot more powerful. Same here, but I don't think it matters whether using `git merge` or the Github GUI to do it, there's still a need to change the default merge message (apparently). Issue on github is, that you aren't able to change the first line ... Cheers, Frank -- http://frank.uvena.de/en/ pgplQylGebuYv.pgp Description: PGP signature ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] Where have the thirdparty plugins gone?
Am 02.03.2012 04:11, schrieb Lex Trotman: Well, thats up to the new maintainer. IIUC the idea was that plugins could be housed in the geany-plugins repo so people could find them, but not have the be part of the combined plugins if the developer did not want, or was unable to meet, the build or release schedule requirements of the combined release. Maybe Frank can say what the arrangement is intended to be now git does things differently? Nope. We just don't use the sourceforge svn anymore and the geany-plugins github roject is for the combined plugins release only. So its a bit cleaned up. BTW: (I think) All other plugins inside the svn has been officially deprecated or moved into geany-plugins combined plugins project. Cheers, Frank ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
[Geany-devel] Looking for some more content for newsletter
Hi folks, Its been a while since we published latest newsletter. A lot happen inside community since but I need someone who like to write down something of it. Yes! I need YOU contributing to the upcoming newsletter ;) Does anyone have any addition content for the newsletter? Cheers, Frank ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] Commit messages on merges
Am 27.02.2012 08:44, schrieb Lex Trotman: [...] I guess if we can filter out merge commits and only show the real commit information it should be good? (See other message with individual commit messages) Yeah, IMO git gives us lots of un-needed merge messages, not much more we can really say other than merged master into branch, so we will have to filter them for human consumption in newsletters anyway. It's not git. It's most likely githubs's webinterface which is causing the entries I'm not happy about. Using command line git merge -m I just did some cool stuff would be a bit better. Now git log e.g. looks like commit 3bcd7fc40078efd601f0e9bed8efec971d505db2 Merge: 3d4e8b4 5cc8a96 Author: Matthew Brush mbr...@codebrainz.ca Date: Sun Feb 26 21:04:50 2012 -0800 Merge pull request #19 from techee/fixes Fixes commit 3d4e8b41d419255ee1b0764fb60e45ea588bd800 Merge: d7d5a6d ca9dca9 Author: Matthew Brush mbr...@codebrainz.ca Date: Sun Feb 26 20:50:01 2012 -0800 Merge pull request #25 from techee/project_patches Project patches The alternative is to always re-base before committing merged branches to master, which is probably better since we don't care how the developer got to the end point and all the commits and merges she made on the way, we just care what the commit to master does. No. This will remove most probably of e.g. additional contributors. Cheers, Frank signature.asc Description: OpenPGP digital signature ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] Patch for Feature Request #3481844
Am 26.02.2012 02:05, schrieb Matthew Brush: On 12-02-25 04:29 PM, Michael Hall wrote: On 02/25/2012 06:00 PM, Colomban Wendling wrote: 2) Is this a general-purpose change or a patch that only should be in Ubuntu? I mean, I don't know of any other distribution using Unity so I'm not 100% sure this should be applied upstream... To my knowledge Unity has been successfully ported to both ArchLinux and OpenSuse, and is in the process of being ported to Fedora as well. It may not be as popular outside of Ubuntu, but it does exist in other distros, so I'd rather get this upstream where everybody can benefit. IMO, it's fine to add it as long as it doesn't cause any issues with non-Unity desktop environments. Have you tested it in Xfce/KDE/GNOME/etc. by any chance or are you pretty sure it won't harm? Going to test it for a couple of days on Xubuntu and Debian with Xfce... Cheers, Frank signature.asc Description: OpenPGP digital signature ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
[Geany-devel] Commit messages on merges
Hi folks, Just something I thought on last merges based on Jiri's patches. Its hard to understand what this merges do just by reading the commit message. Given, that we want to create the ChangeLog based on git log it will be nearly impossible to create a good ChangeLog/Newsfile if we don't keep care. Not sure how, but can we be more verbose here? Cheers, Frank ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] Plugins Guidance
Am 23.02.2012 05:42, schrieb Lex Trotman: Maybe there should be a filetype specific top level item too, where all the language specific plugins could put stuff, and over time we could migrate language specific things to it. I already did start something like this with LaTeX and BibTeX from GeanyLaTeX. So I second this. Cheers, Frank signature.asc Description: OpenPGP digital signature ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] Plugins Guidance
Am 21.02.2012 11:53, schrieb Thomas Martitz: Am 21.02.2012 05:15, schrieb Lex Trotman: 2. don't spread menu items through the Geany menus, users don't know where to look and if several plugins add things to the same place the menu may become unworkable. You don't know what other plugins the user will enable at the same time. You don't propose a solution. What would be the correct place for menu items? Also I don't quite get what you're trying to say. You seem to say both, spreading menu items and adding them to the same place is unworkable, but that contradicts. Current best practice is to append it into tools-menu and / or adding with good reasons directly into menubar. Cheers, Frank ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] Maintainerrequest: Geany-Mini-Script
Am 05.02.2012 11:43, schrieb Eugene Arshinov: I sent a pull request [1] which contains the plugin integrated into geany-plugins. Review and pull, if you wish. I also created a repository [2] which contains geany-mini-script plugin at the state in which it was in SVN repo. Cool. Will you take over maintainership of the code? If so, can do also an update on MAINTAINERS? Cheers, Frank signature.asc Description: OpenPGP digital signature ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] get build command from a plugin
On Mon, 30 Jan 2012 15:16:35 -0800 Matthew Brush mbr...@codebrainz.ca wrote: On 01/28/2012 06:08 AM, Dimitar Zhekov wrote: Hi, How can I $subject? FWIW, I also have a need for this for an Android plugin I'm working on (using Eclipse is sooo painful). So far I've found a need to both get and set the build commands for a project (and the working dir) and also to programmatically cause them to run (IIRC this is already working by a keybindings hack). Would like to have some way to mess arround with build commands also for geanylatex for e.g. having a master document etc. Cheers, Frank -- http://frank.uvena.de/en/ pgpAxU9VXLnZM.pgp Description: PGP signature ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] Geany-Plugins: MAINTAINERS file
On Wed, 11 Jan 2012 19:05:30 -0800 Matthew Brush mbr...@codebrainz.ca wrote: On 01/11/2012 05:13 AM, Frank Lanitz wrote: Am 10.01.2012 23:46, schrieb Matthew Brush: On 01/07/2012 07:20 AM, Colomban Wendling wrote: Le 07/01/2012 16:00, Frank Lanitz a écrit : On Fri, 6 Jan 2012 23:42:39 +0100 Frank Lanitzfr...@frank.uvena.de wrote: * What's the exact difference between Supported and Maintained? The only difference I see is that supported has the word paid in the description, but I doubt that most of us get paid for this in particular, and I also doubt it changes anything on how good is the support (hobby vs. job). My fault. I wanted to change this but missed it. I wanted to s/supported/paid for ... (Even I don't know anybody at the moment who is getting paid with Geany stuff ;) ) I suggest to use paid instead of supported and change current usage of supported to maintained. I'm still not sure what that fact someone is paid or not changes, but otherwise it looks fine and clearer to me. +1 Whether paid or volunteer, it's still Maintained. I suggest dropping the Paid status altogether if no one has used it by the time all the plugins' info is filled in. I disagree. Currently there might be no plugin maintainer being paid to work on a plugin, but: - this might change (...) - is something user should be able to see to resynch there demandings with reality. Hehehe, well said. OK, it's not a big deal, though I still feel it's not very useful for Geany-Plugins. Well, I will purge it for the meanwhile. We can add it once it comes back up again. Cheers, Frank -- http://frank.uvena.de/en/ pgp3xlRoFRnD0.pgp Description: PGP signature ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] Geany-Plugins: MAINTAINERS file
Am 12.01.2012 04:05, schrieb Matthew Brush: You aren't kidding! I was reading a bug report[1] on Pidgin's tracker a while back about the auto-sizing of a text box or something and the tone was absolutely incredible, including demands, threats, name-calling and much more. I couldn't work on a project like Pidgin with so many disrespectful users. Yepp. And also disrespectful companies. E.g. it seems a bit like Oracle and a couple of others are using Pidgin somewhere internally (which is good for sure), but looks a bit like they are communicating: ask @support mailing list ... But we are changing topics ;D Cheers, Frank ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
[Geany-devel] Any content for next newsletter release?
Hi folks, Its been a couple of weeks since last newsletter release and I'm thinking of preparing a new one. As always in this state: Anybody any content which would fit into? If so, maybe you can just send your article to me or use the github capabilities at https://github.com/geany/newsletter Would be cool ;) Cheers, Frank ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] Geany-Plugins: MAINTAINERS file
Am 10.01.2012 23:46, schrieb Matthew Brush: On 01/07/2012 07:20 AM, Colomban Wendling wrote: Le 07/01/2012 16:00, Frank Lanitz a écrit : On Fri, 6 Jan 2012 23:42:39 +0100 Frank Lanitzfr...@frank.uvena.de wrote: * What's the exact difference between Supported and Maintained? The only difference I see is that supported has the word paid in the description, but I doubt that most of us get paid for this in particular, and I also doubt it changes anything on how good is the support (hobby vs. job). My fault. I wanted to change this but missed it. I wanted to s/supported/paid for ... (Even I don't know anybody at the moment who is getting paid with Geany stuff ;) ) I suggest to use paid instead of supported and change current usage of supported to maintained. I'm still not sure what that fact someone is paid or not changes, but otherwise it looks fine and clearer to me. +1 Whether paid or volunteer, it's still Maintained. I suggest dropping the Paid status altogether if no one has used it by the time all the plugins' info is filled in. I disagree. Currently there might be no plugin maintainer being paid to work on a plugin, but: - this might change (...) - is something user should be able to see to resynch there demandings with reality. I'm reading e.g. support@pidgin mailing list and more than once a week I need to facepalm myself because of users don't understand they are not talking to some paid support. I really don't want to end up on Geany with such situation. Cheers, Frank ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] Geany-Plugins: MAINTAINERS file
On Fri, 6 Jan 2012 23:42:39 +0100 Frank Lanitz fr...@frank.uvena.de wrote: * What's the exact difference between Supported and Maintained? The only difference I see is that supported has the word paid in the description, but I doubt that most of us get paid for this in particular, and I also doubt it changes anything on how good is the support (hobby vs. job). My fault. I wanted to change this but missed it. I wanted to s/supported/paid for ... (Even I don't know anybody at the moment who is getting paid with Geany stuff ;) ) I suggest to use paid instead of supported and change current usage of supported to maintained. Cheers, Frank -- http://frank.uvena.de/en/ pgpYT2is6fZNZ.pgp Description: PGP signature ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
[Geany-devel] Geany-Plugins: MAINTAINERS file
Hi folks, We have just added a MAINTAINERS into git to add a single point to find who is responsible for a plugin. Please be so kind and sending in patches or updating the file on your own for your plugins to show who is maintaining etc. File contains a little header with very brief instructions to do so. Cheers, Frank ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] Geany-Plugins: MAINTAINERS file
On Fri, 06 Jan 2012 18:15:32 +0100 Colomban Wendling lists@herbesfolles.org wrote: Le 06/01/2012 10:29, Frank Lanitz a écrit : Hi folks, We have just added a MAINTAINERS into git to add a single point to find who is responsible for a plugin. Please be so kind and sending in patches or updating the file on your own for your plugins to show who is maintaining etc. File contains a little header with very brief instructions to do so. Oops sorry, I completely forgot to do it myself. Now done. Just a few questions: * What's the exact difference between P and M? Do we really expect to have a maintainer but somebody else that deals with the patches? Well... maybe the maintainer likes to get the patches sent to a team or a mailing list. * What's the exact difference between Supported and Maintained? The only difference I see is that supported has the word paid in the description, but I doubt that most of us get paid for this in particular, and I also doubt it changes anything on how good is the support (hobby vs. job). My fault. I wanted to change this but missed it. I wanted to s/supported/paid for ... (Even I don't know anybody at the moment who is getting paid with Geany stuff ;) ) Cheers, Frank -- http://frank.uvena.de/en/ pgph7zgiPH5OE.pgp Description: PGP signature ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] Issue with geanyLaTeX after GtkBuilder: Help needed to debug
On Tue, 03 Jan 2012 08:45:38 -0800 Matthew Brush mbr...@codebrainz.ca wrote: On 12/31/2011 02:57 AM, Frank Lanitz wrote: Hi folks, Since about GtkBuilder come in into Geany core we are experiencing some issue with GeanyLaTeX in terms of in some cases the toolbar is not able tobe loaded and Geany is ending up inside a segfault. Most likely its repreducable by activating the toolbar and restarting Geany having a tex-file loaded. The issue seems to be located in near of line https://github.com/geany/geany-plugins/blob/master/geanylatex/src/geanylatex.c#L168 unfortunately I don't have any bloody idea, what might is going wrong. Anyone else could jump in here? Attached is a patch to fix the issue. It's the same bug in Geany where this code was probably copied from, so I'll fix Geany and leave it to you to apply this patch to the plugin. If either Geany or GeanyLatex is fixed the plugin will be fixed, but for correctness I guess they should both be fixed. IIUC what's happening is Geany's variable (toolbar.c:toolbar_markup) is declared const but not static so it's global to the entire program. When the plugin is loaded (at runtime with dlopen) with the same variable name also declared const, the one previously defined in Geany is used instead. If Geany's is declared static, GeanyLatex uses it's own variable because it can't see Geany's, if it's declared static in GeanyLatex, the local scope wins I guess. So what was happening was GeanyLatex was loading Geany's toolbar XML string constant instead of it's own (which obviously is a problem). Yepp. Sounds legit. I'd love to know why this changed all of the sudden though, why it's different from before. Me too ;) -- http://frank.uvena.de/en/ pgpIsINMArm48.pgp Description: PGP signature ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] Issue with geanyLaTeX after GtkBuilder: Help needed to debug
On Tue, 03 Jan 2012 09:01:06 -0800 Matthew Brush mbr...@codebrainz.ca wrote: On 01/03/2012 08:45 AM, Matthew Brush wrote: On 12/31/2011 02:57 AM, Frank Lanitz wrote: Hi folks, Since about GtkBuilder come in into Geany core we are experiencing some issue with GeanyLaTeX in terms of in some cases the toolbar is not able tobe loaded and Geany is ending up inside a segfault. Most likely its repreducable by activating the toolbar and restarting Geany having a tex-file loaded. The issue seems to be located in near of line https://github.com/geany/geany-plugins/blob/master/geanylatex/src/geanylatex.c#L168 unfortunately I don't have any bloody idea, what might is going wrong. Anyone else could jump in here? Attached is a patch to fix the issue. It's the same bug in Geany where this code was probably copied from, so I'll fix Geany and leave it to you to apply this patch to the plugin. If either Geany or GeanyLatex is fixed the plugin will be fixed, but for correctness I guess they should both be fixed. IIUC what's happening is Geany's variable (toolbar.c:toolbar_markup) is declared const but not static so it's global to the entire program. When the plugin is loaded (at runtime with dlopen) with the same variable name also declared const, the one previously defined in Geany is used instead. If Geany's is declared static, GeanyLatex uses it's own variable because it can't see Geany's, if it's declared static in GeanyLatex, the local scope wins I guess. So what was happening was GeanyLatex was loading Geany's toolbar XML string constant instead of it's own (which obviously is a problem). I'd love to know why this changed all of the sudden though, why it's different from before. I fixed in Geany in this commit: https://github.com/geany/geany/commit/8f489fc9fbab8a8c197f40536fac8ebd74c430eb So if you pull from Geany's repo and rebuild, even before applying the patch, the toolbar problem should be fixed, but probably best to apply the same changes as in that commit the plugin as well. Thanks for the finding. I've applied it locally and will give it a test. Cheers, Frank -- http://frank.uvena.de/en/ pgpUy7BGCS6Gg.pgp Description: PGP signature ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] Issue with geanyLaTeX after GtkBuilder: Help needed to debug
On Sat, 31 Dec 2011 04:09:36 -0800 Matthew Brush mbr...@codebrainz.ca wrote: Will check it out in a while and see if I can spot anything. Would be cool as I really don't have any clue what might can be broken. I assume its some issue on my code ... but :D Cheers, Frank -- http://frank.uvena.de/en/ pgpWDDpZZK3YH.pgp Description: PGP signature ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
[Geany-devel] Just another github question: Easy way to pull pull reuqest for testing purposes?
Hi folks, During the last weeks I merged a couple of pull requests into geany-plugins. During this work I found it a bit annoying not finding a easy way to pull the pull request directly and test it locally and maybe add it to me git repo. Is there any direct way on doing this instead of going to offerer's github page and clone the complete repo? Cheers, Frank -- http://frank.uvena.de/en/ pgpJmpZMHrDhj.pgp Description: PGP signature ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
[Geany-devel] Issue with geanyLaTeX after GtkBuilder: Help needed to debug
Hi folks, Since about GtkBuilder come in into Geany core we are experiencing some issue with GeanyLaTeX in terms of in some cases the toolbar is not able tobe loaded and Geany is ending up inside a segfault. Most likely its repreducable by activating the toolbar and restarting Geany having a tex-file loaded. The issue seems to be located in near of line https://github.com/geany/geany-plugins/blob/master/geanylatex/src/geanylatex.c#L168 unfortunately I don't have any bloody idea, what might is going wrong. Anyone else could jump in here? Cheers, Frank -- http://frank.uvena.de/en/ pgpZFWRuCDDPB.pgp Description: PGP signature ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] Issue with geanyLaTeX after GtkBuilder: Help needed to debug
On Sat, 31 Dec 2011 03:04:13 -0800 Matthew Brush mbr...@codebrainz.ca wrote: On 12/31/2011 02:57 AM, Frank Lanitz wrote: Hi folks, Since about GtkBuilder come in into Geany core we are experiencing some issue with GeanyLaTeX in terms of in some cases the toolbar is not able tobe loaded and Geany is ending up inside a segfault. Most likely its repreducable by activating the toolbar and restarting Geany having a tex-file loaded. The issue seems to be located in near of line https://github.com/geany/geany-plugins/blob/master/geanylatex/src/geanylatex.c#L168 unfortunately I don't have any bloody idea, what might is going wrong. Anyone else could jump in here? Can you post a full traceback from gdb with debugging symbols? IIRC the toolbar was already using GtkBuilder and is not in the same .glade file as the rest of the UI (and theoretically shouldn't be affected by it). Dammit. With current geany build I cannot reproduce the crash, only a huge number of warnings Geany-INFO: Loaded: /home/frlan/local/lib/geany/geanylatex.so (GeanyLaTeX) (geany:10190): Gtk-CRITICAL **: IA__gtk_action_get_sensitive: assertion `GTK_IS_ACTION (action)' failed (geany:10190): Gtk-CRITICAL **: IA__gtk_action_get_sensitive: assertion `GTK_IS_ACTION (action)' failed (geany:10190): Gtk-CRITICAL **: IA__gtk_action_get_sensitive: assertion `GTK_IS_ACTION (action)' failed (geany:10190): Gtk-CRITICAL **: IA__gtk_action_get_sensitive: assertion `GTK_IS_ACTION (action)' failed (geany:10190): Gtk-CRITICAL **: IA__gtk_action_get_sensitive: assertion `GTK_IS_ACTION (action)' failed (geany:10190): Gtk-CRITICAL **: IA__gtk_action_get_sensitive: assertion `GTK_IS_ACTION (action)' failed After I activated the toolbar inside plugin configuration dialog I got: Gtk-WARNING **: New: missing action New Program received signal SIGTRAP, Trace/breakpoint trap. 0x7540b888 in g_logv () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 (gdb) bt #0 0x7540b888 in g_logv () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7540bc02 in g_log () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x779ebda2 in ?? () from /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0 #3 0x779eba05 in ?? () from /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0 #4 0x779eba05 in ?? () from /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0 #5 0x779ef431 in gtk_ui_manager_ensure_update () from /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0 #6 0x779ef4a9 in ?? () from /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0 #7 0x70ab0ab9 in init_toolbar () at geanylatex.c:172 #8 0x70ab3a47 in on_configure_response (dialog=optimized out, response=optimized out, user_data=optimized out) at geanylatex.c:253 #9 on_configure_response (dialog=optimized out, response=optimized out, user_data=optimized out) at geanylatex.c:183 #10 0x75cd3804 in g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 #11 0x75ce578a in ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 #12 0x75ceee11 in g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 #13 0x75ceefb2 in g_signal_emit () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 #14 0x75cd3804 in g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 #15 0x75ce578a in ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 #16 0x75ceee11 in g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 #17 0x75ceefb2 in g_signal_emit () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 #18 0x77833dc5 in ?? () from /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0 #19 0x75cd375a in g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 #20 0x75ce4f7a in ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 #21 0x75ceee11 in g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 #22 0x75ceefb2 in g_signal_emit () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 #23 0x77832bed in ?? () from /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0 #24 0x778dc418 in ?? () from /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0 #25 0x75cd375a in g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 #26 0x75ce55bf in ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 #27 0x75ceebe3 in g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 #28 0x75ceefb2 in g_signal_emit () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 #29 0x779f5301 in ?? () from /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0 #30 0x778da5d3 in gtk_propagate_event () from /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0 #31 0x778da933 in gtk_main_do_event () from /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0 #32 0x7754621c in ?? () from /usr/lib
[Geany-devel] Looking for maintainer for treebrowser plugin
Hi folks, I've just received the bad news the Adrian will not be able to maintain treebowser plugin in future. As its plugin adding a nice feature it would be a bad thing if its dying. Does anyone of you like to take over maintainer role for that plugin? Cheers, Frank -- http://frank.uvena.de/en/ pgpHG2DPejPwA.pgp Description: PGP signature ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] Geany-Plugins: Adding a maintainer file
Am 17.12.2011 16:12, schrieb Frank Lanitz: Hi folks, What do you think of adding a maintainer file, which basically include only three information: plugin-name, maintainer name, contact email. Well, I'd like to extend the point and suggest based on linux kernel maintainer file: An entry shall include the plugin name and Descriptions of section entries: P: Person M: Mail patches to: FullName address@domain W: Web-page with status/info S: Status, one of the following: Supported: Someone is actually paid to look after this. Maintained: Someone actually looks after it. Odd Fixes: It has a maintainer but they don't have time to do much other than throw the odd patch in. See below.. Orphan: No current maintainer [but maybe you could take the role as you write your new code]. Obsolete:Old code. Something tagged obsolete generally means it has been replaced by a better system and you should be using that. Comments? Cheers, Frank -- http://frank.uvena.de/en/ pgpsoz3bV9oTM.pgp Description: PGP signature ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] Geany-Plugins: git repo up and running
On Fri, 30 Dec 2011 10:44:24 +0100 Thomas Martitz thomas.mart...@student.htw-berlin.de wrote: Am 19.12.2011 20:05, schrieb Frank Lanitz: Well.. I would like to see process as I described. But as there have been a lot of comments on I'm not sure whether its wished at all. Well, it appears nobody strictly disagrees with this policy. So, I'd say it's up to you to enforce it. OK. So its law :D Cheers, Frank -- http://frank.uvena.de/en/ pgpkrCnak9rph.pgp Description: PGP signature ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] autocompletion plugins API
On Wed, 21 Dec 2011 20:24:20 +0200 Gordio gordi.o...@gmail.com wrote: Hi, All. Geany have API for work with autocompletion list? There is a tag file avaialble on http://wiki.geany.org/tags/start#c_tags which introduces common symbols provided by plugin API. Cheers, Frank -- http://frank.uvena.de/en/ pgpV0jAUq5Om1.pgp Description: PGP signature ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] Geany-Plugins: git repo up and running
On Sun, 18 Dec 2011 19:01:13 +0100 Thomas Martitz thomas.mart...@student.htw-berlin.de wrote: So, what is the policy for geany-plugins now? Can everybody push to the master repo as it was with svn, or did we switch to the pull-style where Frank would pull changes from the maintainers repos (changes in the common part or the plugin for a release)? Well.. I would like to see process as I described. But as there have been a lot of comments on I'm not sure whether its wished at all. Cheers, Frank -- http://frank.uvena.de/en/ pgpAzl3OqHyqu.pgp Description: PGP signature ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
[Geany-devel] Geany-Plugins: Adding a maintainer file
Hi folks, What do you think of adding a maintainer file, which basically include only three information: plugin-name, maintainer name, contact email. Cheers, Frank -- http://frank.uvena.de/en/ pgpwvqfqGRnHA.pgp Description: PGP signature ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] push access to plugins at github
Am 15.12.2011 10:46, schrieb Alexander Petukhov: Can I be given a push access to the plugins repository? github user - cesspit done. Cheers, Frank ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] [geanyprj] coding style patch
Am 13.12.2011 09:11, schrieb Matthew Brush: On 12/12/2011 11:02 PM, Yura Siamashka wrote: Hi Sorry I didn't follow conversion to github and I am not really familiar with new workflow. So as GeanyPrj maintainer how do I commit patch to mainline? Should my github user be added to main geany-plugins repository or I need to create new fork with related changes and create pull request to main geany-plugins from time to time? I think Frank asked for Github usernames in another thread for this. This github stuff is a bit confusing for me. There was some discussion about doing something like this: 1. Go to github.com/geany/geany-plugins and click Fork 2. Go to github.com/you/geany-plugins and get the clone URL 3. From terminal: $ git clone address from github in step 2 $ cd geany-plugins/geanyprj $ git checkout -b your-topic-branch hack, commit, hack, commit, ... 4. git push origin your-topic-branch 5. Go to github.com/you/geany-plugins/tree/your-topic-branch and click the Pull Request button. Or we might end up just working from the main repository ourselves like we did with SVN, unless someone can step up to review all the pull requests. Frank did you decide on a best practice yet? I'd really like to see the workflow as you described inside the numbered section. But as I'm not god its a bit up to community what's the best way ;) Cheers, Frank ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] Geany-Plugins: git repo up and running
Am 12.12.2011 22:36, schrieb Jiří Techet: On Mon, Dec 12, 2011 at 14:54, Frank Lanitz fr...@frank.uvena.de wrote: Hi folks, Just I case you missed the news inside the threads: the new git repo for geany-plugins is online and can be found at https://github.com/geany/geany-plugins Hi Frank, it looks you have forgotten to push the 0.18 branch - you need to use git push --all origin to push all the branches. Yepp, you are right. My wrong. Will do it soonish. Cheers, Frank ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] Just a stupid github question: How to merge a pull request with fast forward?
Am 13.12.2011 09:51, schrieb Nathan Broadbent: See question from subject line. How can I merge a pull request without adding a new commit stating the merge? Is there some kind of ff or cherry-pick available through front end? You can't do a cherry pick or rebase through the front-end. I think adding this 'merge pull request' commit is a good idea, since it shows more information about where the commit came from. OK. So I assume its best practice also on github to do so? But if you want, you can use 'git rebase' to avoid the merge commit. In the case of my 'gitignore' branch, you could have run the following commands: git remote add ndbroadbent git://github.com/ndbroadbent/geany-plugins.git http://github.com/ndbroadbent/geany-plugins.git git fetch ndbroadbent git rebase ndbroadbent/gitignore git remote rm ndbroadbent Yepp. This I was aware of. Just wondeirng, wehther it can be done via github. Cheers, Frank ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
[Geany-devel] Geany-Plugins: git repo up and running
Hi folks, Just I case you missed the news inside the threads: the new git repo for geany-plugins is online and can be found at https://github.com/geany/geany-plugins Cheers, Frank ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] GtkBuilder is in!
Am 11.12.2011 01:21, schrieb Matthew Brush: - more testing on win32 Current nightly build of 12/12/11 did not start do to missing symbol on my box. A screenshot from my German Windows 7: http://frank.uvena.de/tmp/geany_error.png Its telling: g_malloc0_n wasn't found inside libglib-2.0-0.dll. Cheers, Frank signature.asc Description: OpenPGP digital signature ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] GtkBuilder is in!
Am 13.12.2011 07:22, schrieb Matthew Brush: On 12/12/2011 10:14 PM, Frank Lanitz wrote: Am 11.12.2011 01:21, schrieb Matthew Brush: - more testing on win32 Current nightly build of 12/12/11 did not start do to missing symbol on my box. A screenshot from my German Windows 7: http://frank.uvena.de/tmp/geany_error.png Its telling: g_malloc0_n wasn't found inside libglib-2.0-0.dll. I think this is the same issue that Thomas noticed[1] (before the gtkbuilder merge). I'm pretty sure it's not a problem with Geany itself but rather GTK+ or the way Geany is built/linked for Windows. I just updated from nightly zip so I don't think its a Gtk 2.24 issue alone. Cheers, Frank signature.asc Description: OpenPGP digital signature ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] geany-plugins converted to git
On Fri, 9 Dec 2011 21:43:56 +0100 Jiří Techet tec...@gmail.com wrote: On Thu, Dec 8, 2011 at 00:05, Colomban Wendling lists@herbesfolles.org wrote: Le 07/12/2011 22:54, Jiří Techet a écrit : Hi, I've completed the conversion of geany-plugins to git, the repository can be found here: https://github.com/techee/geany-plugins As with Geany's repository conversion, please have a look at it and don't use/fork it until more people check everything is alright and the repository is moved to its final location. 5bff19ecea993d9d2c3038efcfba63fecdc3342e and f3a667d624d31aec778e2ababeac96c25f6c5169 are the same commit, but it seems there was a tag created (r858), then removed (r861), and then crated again after a new commit (r863), so it's actually weird; not in the exact same way, but I don't thing it's a real problem. That's true. If you prefer, I've just created a new repository without the useless side-branch before 0.17.1 https://github.com/techee/geany-plugins2 Looks a bit nicer. You can use whichever repository you prefer. Looks nicer. Would take geany-plugins2 repo. Any objectives? Cheers, Frank -- http://frank.uvena.de/en/ pgp7YMEDBQfIJ.pgp Description: PGP signature ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] statusbar virtual column
Hi, On Wed, 3 Aug 2011 20:04:18 +0300 Dimitar Zhekov dimitar.zhe...@gmail.com wrote: As you may have noticed, when cursor is in the virtual space (beyond eoln), our status bar always shows the last real column. This small patch adds a new %v (and %V) format specification, which displays a virtual column number, as if the line extends to the cursor position. I haven't included sci_get_cursor_virtual_space() is the plugin interface for now. Since the virtual position normally requires 3 SSM()-s, and is less likely to be used than the line and column, I placed the calls into add_statusbar_statistics() instead of ui_update_statusbar(). Has this patch been applied and or commented at some place? Cheers, Frank -- http://frank.uvena.de/en/ pgpoZzCfwgyia.pgp Description: PGP signature ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] geany-plugins converted to git
On Sat, 10 Dec 2011 09:50:25 +0100 Frank Lanitz fr...@frank.uvena.de wrote: On Fri, 9 Dec 2011 21:43:56 +0100 Jiří Techet tec...@gmail.com wrote: On Thu, Dec 8, 2011 at 00:05, Colomban Wendling lists@herbesfolles.org wrote: Le 07/12/2011 22:54, Jiří Techet a écrit : Hi, I've completed the conversion of geany-plugins to git, the repository can be found here: https://github.com/techee/geany-plugins As with Geany's repository conversion, please have a look at it and don't use/fork it until more people check everything is alright and the repository is moved to its final location. 5bff19ecea993d9d2c3038efcfba63fecdc3342e and f3a667d624d31aec778e2ababeac96c25f6c5169 are the same commit, but it seems there was a tag created (r858), then removed (r861), and then crated again after a new commit (r863), so it's actually weird; not in the exact same way, but I don't thing it's a real problem. That's true. If you prefer, I've just created a new repository without the useless side-branch before 0.17.1 https://github.com/techee/geany-plugins2 Looks a bit nicer. You can use whichever repository you prefer. Looks nicer. Would take geany-plugins2 repo. Any objectives? OK. I've just pushed to https://github.com/geany/geany-plugins Have fun ;) Cheers, Frank -- http://frank.uvena.de/en/ pgpFEGdjR5FmJ.pgp Description: PGP signature ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] geany-plugins converted to git
Am 08.12.2011 00:05, schrieb Colomban Wendling: Le 07/12/2011 22:54, Jiří Techet a écrit : Hi, I've completed the conversion of geany-plugins to git, the repository can be found here: https://github.com/techee/geany-plugins As with Geany's repository conversion, please have a look at it and don't use/fork it until more people check everything is alright and the repository is moved to its final location. 5bff19ecea993d9d2c3038efcfba63fecdc3342e and f3a667d624d31aec778e2ababeac96c25f6c5169 are the same commit, but it seems there was a tag created (r858), then removed (r861), and then crated again after a new commit (r863), so it's actually weird; not in the exact same way, but I don't thing it's a real problem. Apart that, I don't see any problem watching the history tree :) Me neither. Good work from my point of view. The 0.17.1-0.18 was a bit a messup on creating branch etc. Rest looks pretty fine to me. I suggest: If there are no issues found by anyone till Friday, we can push it to official repo. Thanks for efforts, Jiri! Cheers, Frank signature.asc Description: OpenPGP digital signature ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
[Geany-devel] Geany-Plugins: Git-transition
Hi developers, Jire and I just finally scheduled git transition of the plugins. This will be done Wednesday evening CET. Please be so kind and stop committing to svn so we can ensure, all changes are going in. Please let me also know you github accounts if available for committing to plugins etc. Cheers, Frank ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] Geany-Plugins: Git-transition
Am 06.12.2011 09:06, schrieb Frank Lanitz: Jire and ... It's Jiri... sorry. Cheers, Frank ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
[Geany-devel] Geany-Plugins: SVN-URL on git
Hi, I didn't found the conclusion on the discussion: What was the outcome on this topic? Which reference to old svn shall be inserted into git repo? Cheers, Frank -- http://frank.uvena.de/en/ pgprIJqz7bQrv.pgp Description: PGP signature ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] (no subject)
Am 02.12.2011 01:20, schrieb Lex Trotman: On Fri, Dec 2, 2011 at 10:54 AM, Meyer 3m.me...@gmail.com wrote: Sure. I want to be able to select text, and then insert a character (e.g. an apostrophe) before and after the selection just by pressing the apostrophe key. Since the normal behavior when a character is pressed while text is selected is to delete the text and insert a character, I need to know when that happens - then I could undo the delete and insert my characters. If it was two separate events though - delete then insert - I won't want to do anything. I have it working now, but it seems awfully hackish: when one of the characters I might insert is pressed, I store the current position of the cursor and undo the last event. If the new cursor position is the same place as the old one, then it was a overwrite event. Otherwise, it was delete then insert. So, any ideas for how I could do this would be much appreciated! I assume you are writing a plugin. You should use the keybinding system to capture the apostrophe before it goes to scintilla so you can detect and do anything you want. You could also use editor_nodify signal [1]. E.g. used in GeanyLaTeX plugin for doing something similar. Cheers, Frank [1] http://www.geany.org/manual/reference/pluginsignals_8c.html#af601d8beb39bf8082ddd1c09c74ce892 ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
[Geany-devel] ReST: Image size
Hi folks, Its a bit OT, but wondering whether somebody o you could help me: How can I set sizes for images inside ReST? E.g. I want to set it to 50% of page width? Didn't found anything on documentation Cheers, Frank signature.asc Description: OpenPGP digital signature ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] ReST: Image size
Am 01.12.2011 17:25, schrieb Frank Lanitz: Hi folks, Its a bit OT, but wondering whether somebody o you could help me: How can I set sizes for images inside ReST? E.g. I want to set it to 50% of page width? Didn't found anything on documentation I found a way doing it by :height: but this is creating a broken LaTeX for pdf generation. Might will need to report that after some more investigation. Cheers, Frank signature.asc Description: OpenPGP digital signature ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] ReST: Image size
Am 01.12.2011 18:01, schrieb Colomban Wendling: Le 01/12/2011 17:55, Frank Lanitz a écrit : Am 01.12.2011 17:25, schrieb Frank Lanitz: Hi folks, Its a bit OT, but wondering whether somebody o you could help me: How can I set sizes for images inside ReST? E.g. I want to set it to 50% of page width? Didn't found anything on documentation I found a way doing it by :height: but this is creating a broken LaTeX for pdf generation. Might will need to report that after some more investigation. This is likely to be caused by the LaTeX output tuning we have (rst2latex.sed), I guess it doesn't handle what :height: generates. Yepp. Good point. Needs to be revisited again. Cheers, Frank signature.asc Description: OpenPGP digital signature ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] ReST: Image size
Am 01.12.2011 18:11, schrieb Frank Lanitz: Am 01.12.2011 18:01, schrieb Colomban Wendling: Le 01/12/2011 17:55, Frank Lanitz a écrit : Am 01.12.2011 17:25, schrieb Frank Lanitz: Hi folks, Its a bit OT, but wondering whether somebody o you could help me: How can I set sizes for images inside ReST? E.g. I want to set it to 50% of page width? Didn't found anything on documentation I found a way doing it by :height: but this is creating a broken LaTeX for pdf generation. Might will need to report that after some more investigation. This is likely to be caused by the LaTeX output tuning we have (rst2latex.sed), I guess it doesn't handle what :height: generates. Yepp. Good point. Needs to be revisited again. Yepp, its really the reasons. Maybe we should revisit the whole minipage again. Unfortunately I don't remember the reasons why we added them. Cheers, Frank signature.asc Description: OpenPGP digital signature ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] ReST: Image size
Am 01.12.2011 18:18, schrieb Colomban Wendling: Le 01/12/2011 18:11, Frank Lanitz a écrit : Am 01.12.2011 18:01, schrieb Colomban Wendling: Le 01/12/2011 17:55, Frank Lanitz a écrit : Am 01.12.2011 17:25, schrieb Frank Lanitz: Hi folks, Its a bit OT, but wondering whether somebody o you could help me: How can I set sizes for images inside ReST? E.g. I want to set it to 50% of page width? Didn't found anything on documentation I found a way doing it by :height: but this is creating a broken LaTeX for pdf generation. Might will need to report that after some more investigation. This is likely to be caused by the LaTeX output tuning we have (rst2latex.sed), I guess it doesn't handle what :height: generates. Yepp. Good point. Needs to be revisited again. I've committed a fix that simply gets rid of any \includegraphics options in the input. This should fix the output validity, but maybe we'd like to use the input options? Hmm... we should ensure options given by rst are taken over to PDF. Cheers, Frank signature.asc Description: OpenPGP digital signature ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] ReST: Image size
Am 01.12.2011 18:42, schrieb Colomban Wendling:
Le 01/12/2011 18:21, Frank Lanitz a écrit :
Am 01.12.2011 18:18, schrieb Colomban Wendling:
Le 01/12/2011 18:11, Frank Lanitz a écrit :
Am 01.12.2011 18:01, schrieb Colomban Wendling:
Le 01/12/2011 17:55, Frank Lanitz a écrit :
Am 01.12.2011 17:25, schrieb Frank Lanitz:
Hi folks,
Its a bit OT, but wondering whether somebody o you could help me: How
can I set sizes for images inside ReST? E.g. I want to set it to 50% of
page width? Didn't found anything on documentation
I found a way doing it by :height: but this is creating a broken LaTeX
for pdf generation. Might will need to report that after some more
investigation.
This is likely to be caused by the LaTeX output tuning we have
(rst2latex.sed), I guess it doesn't handle what :height: generates.
Yepp. Good point. Needs to be revisited again.
I've committed a fix that simply gets rid of any \includegraphics
options in the input. This should fix the output validity, but maybe
we'd like to use the input options?
Hmm... we should ensure options given by rst are taken over to PDF.
OK. Is \command[option1,option2,]{...} valid (e.g. a trailing comma)?
If yes it's easy, otherwise... :(
Tralling , is not very often valid ;)
Well. I guess I will finish the current newsletter with some extra
effort and we can hack a bit after that... I can provide updated
tex-file also.
Cheers,
Frank
signature.asc
Description: OpenPGP digital signature
___
Geany-devel mailing list
Geany-devel@uvena.de
https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] (no subject)
Am 01.12.2011 20:57, schrieb Meyer: I have two possible situations that I need to differentiate between, and I'm not sure how to do it - The first situation is the user deletes selected text by overwriting it with a new character. The second is the user deletes selected text by pressing backspace/delete, and then enters a new character. I thought this would be fairly easy, but I've been trying to figure it out for awhile and haven't gotten anywhere. Does anyone have any ideas for how I could accomplish this? Can you go into more details in which context you need that information? Cheers, Frank signature.asc Description: OpenPGP digital signature ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] Unit tests for Geany (continued from Github)
Am 30.11.2011 08:39, schrieb Matthew Brush: On 11/29/2011 11:12 PM, Frank Lanitz wrote: Am 30.11.2011 07:36, schrieb Nathan Broadbent: P.S. The documentation needs to be updated for the 'waf' build system, in quite a few places, including geany-plugins. I don't refer to other points as I would need to catch up discussion on github before (wth why are we using differnt chanels? can we turn off the github commenting stuff.. its a nightmare) It's not a nightmare if you use it. Comments are essential for code review, pull requests and useful for discussion of specific code. You can configure your Github notifications to email you just about everything and you can reply using your email client, if it's too much trouble bouncing between web browser and email client. I activated things I know of and still got feeling, don't receive everything. E.g. the discussion about Ruby stuff I only received one mail. Nathan made a pull request, he was told the proper channels (upstream) since it was a Scintilla change, then he asked about testing and was directed to the ML to discuss it. If you aren't able to open your web browser, that pretty much sums up the relevant discussion on the pull request comments. Thanks for writing down conclusion. Cheers, Frank ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] Unit tests for Geany (continued from Github)
Am 30.11.2011 10:11, schrieb Matthew Brush: On 11/30/2011 12:55 AM, Nathan Broadbent wrote: I've figured out why the installation documentation didn't work for me: You pre-generate the 'configure' script and package this when you distribute a release in a tarball, but this configure script isn't checked into the repository. I checked out the source-code from github, but the documentation doesn't mention anything about running './autogen.sh' first. (Sorry, I haven't done much C programming for a while...) Since the project has moved to Github, more people will be getting the source code straight from the repository. So it might be helpful to replace $ ./configure with $ ./autogen.sh in the Autotools based build system section of the manual (http://www.geany.org/manual/current/#installation), and also in the installation section of the README. The ./configure script is automatically generated so it's not so great to check it into the VCS. It is mentioned on the Git page[1] for people who're building development code though. I think the manual is strictly for stable release source code (same with README). I agree. Maybe we could add a section to HACKING file too as it would fit there IMHO. Cheers, Frank ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] Unit tests for Geany (continued from Github)
Am 30.11.2011 10:24, schrieb Lex Trotman: [...] I agree. Maybe we could add a section to HACKING file too as it would fit there IMHO. Since we have a long release cycle lots of non-C speaking people use the Git version, so I think it needs to be where users can see it, not just us developers :) My understanding was that HACKING was the README for them. However, maybe we should add a link between both. I don't think we need to refer inside 'release' README to autogen.sh. Cheers, Frank ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] Unit tests for Geany (continued from Github)
Am 30.11.2011 07:36, schrieb Nathan Broadbent: P.S. The documentation needs to be updated for the 'waf' build system, in quite a few places, including geany-plugins. I don't refer to other points as I would need to catch up discussion on github before (wth why are we using differnt chanels? can we turn off the github commenting stuff.. its a nightmare) However, comments like you do above are not very helpful. If there is a mistake inside documentation, which might can happen - no question - we still don't know where and what might be wrong. Please be so kind and point to the place you did found the issue. Comments like this only causes us to re ask you one and another time and also are giving a bad formating of you hint (read: I'm a bit against you change succession idea before I ever see it which is not a good starting point) Cheers, Frank ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] Unit tests for Geany (continued from Github)
Am 30.11.2011 08:17, schrieb Matthew Brush: To be honest, the real reason that I started talking about unit tests, is because I really need them in order to write a lexer for scintilla. Manual testing for lexers would be a nightmare. That sounds much more approachable than doing it for Geany :) Well... Geany in special Geany-Plugin-API needs such thing as well, but starting at Scintilla (given they don't have such a system - I just don't know) would make sense most. Cheers, Frank ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] Some sort of thoughts about geany-plugins-devel-git-repo
Am 16.11.2011 22:50, schrieb Lex Trotman: [..] I don't think your perception is wrong, but I think that keeping plugins reasonably separate is also a good idea. As a user I can choose the parts I want without the parts I don't need. So only really tiny things should be combined like addons. We talked about this earlier on IRC and the goal of geany-plugins to have one single plugin bucket where plugins are not splitted up. Right now its already possible to build single plugins e.g. by using --enable flag on waf. In other cases, like project management, there is sufficient variation in use-cases that there may be more than one plugin, like how the current project plugins address two slightly differernt uses. Or in some cases there is a natural progression from an old plugin to a new (and hopefully better) one, eg debugger plugins What it needs is a technical solution to allow plugins to build on other plugins. That way the original functionality doesn't need to be re-built, but it introduces dependencies between plugins. Dependencies? I agree. I think introducing changes to core about GObject etc will make such things easier. Currently its far away. Regarding the ideas with separate repos/submodules: This basically breaks what the initial idea of geany-plugins was. To share infrastructure, build system and translations. The combined release idea came actually some time after that. I'm not sure that it prevents any of this, but as I now understand it, GP plugins can't be built separately so, yes, it makes less sense to have separate repos. I agree ;) Cheers, Frank signature.asc Description: OpenPGP digital signature ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] Some sort of thoughts about geany-plugins-devel-git-repo
Am 16.11.2011 12:02, schrieb Alexander Petukhov: Maybe we can use git pre-commit hook to prevent commits that breaks some quality criteria? http://book.git-scm.com/5_git_hooks.html To be honest I didn't get much into details but it seemed to me that it can handle quality check tasks. Well, this will need to maintain the hook e.g. on adding white rules for warnings that are common and don't hurt much. Give we don't add such thing, geanylua, prettyprinter and a bunch of other plugins will not be part of the party. So my suggestion is still to use a single common repo for all plugins and use commit hooks to prevent unqualified code. I diasagree as see above. This requires that at some point all plugins in this repo pass this quality check, and here is what I suggest - move plugins from svn one by one, checking code for quality. For those that didn't pass we can create a distinct repo under geany organization. Once a maintainer or a volunteer refine a code to fit the requirements it can be moved to a main repo. Until then it can be still available but won't be included in g-p release (maybe we can create distinct release geany-plugins-unsupported, as IIUC I already suggested once). In basic thoughts I'm with you. As this will remove a bunch of plugins from repository and split up focus very much I'm afraid I have to disagree. To easily move plugins between probably it's a good idea to use submodules, IIUC this is svn externals analogue. I think submodules is nice for including external libraries into your source tree, but will make things more complicated by none visible extra from my point of view. Its against the idea behind geayn-pluings (see also below). To make every plugin compile and build independently I vote for eliminating common po catalog, that I also suggested recently, this will also help to avoid translations intersection between different plugins. This wasn't the goal behind geany-plugins as wrote in other. The goal was to have one single build system, one single translation and some more common infrastructure. Renaming plugins in sense of removing geany prefix also can be done while moving. This is up to the author of plugin ;D Cheers, Frank signature.asc Description: OpenPGP digital signature ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] Some sort of thoughts about geany-plugins-devel-git-repo
Am 16.11.2011 07:12, schrieb Lex Trotman: 1. Individual plugin maintainers shouldn't care about all the other plugins in the combined release Not a written, but existing rule. 2. Users getting the combined release to build should get everything in one command ACK. 3. The combined release maintainers still need to be able to make changes to each plugin in case of urgent bugfix and temporarily or permanently missing individual plugin maintainer. ACK. 4. Not all plugins are in the combined release, due to quality, timing, or maintainer availability issues. But users rely on plugins so it is bad to remove their availability. ACK Having a single repository with branches fails item 1. since Git can't do partial checkouts/clones so all maintainers have all plugins and have to see all changes, a lot of noise. And accidental changes to parts of the tree outside the users plugin can be committed and pushed. I disagree a bit here. The goal is to have your own branch and work on your own branch for your plugin. Ones this is done you are sending a merge request to $release_team. You will not see whole noise - only if you do a git merge or rebase against master. Of course the commit and push is possible. But release team is asked to block such requests. So I suggest that each plugin needs to have a separate repository under the Geany organisation. The plugin maintainer can fork these for development of their individual plugin in complete freedom and push to the repository when the plugin is ready providing item 1. These repositories also ensure Geany has a copy of the plugin under project control to prevent them disappearing or changing unexpectedly and to allow local bugfixes and quality checks to be made, providing item 3. I understand that access can be limited to specific repos so maintainers can't accidently change another plugin. I did this with GeanyLaTeX, GeanySendMail and some of the others for a while and it wasn't worth as it was twice effort. It will not work out as most of the maintainer currently aren't able to do basic maintenance in time, they will not be able to do extra efforts e.g. for having a local build system which you will need. The combined release has its own repository that refers to the individual plugins ones. Git submodules allow the combined repository to point to specific versions of the individual plugin repositories, perfect for release functionality. Pushes from maintainers are not automatically included in the combined release until they have been quality checked. In general its a good idea, but for geany-plugin's purpose I'm not with you. Unfortunately this violates item 2 since users checking out the combined release need to know to pull the subprojects, a somewhat more esoteric thing than git clone git://github.com/geany-plugins/geany-plugins.git but we can put the necessary command in readme and other places. Other than that only the combined plugin maintainers need to know about the subproject technology, not individual plugin maintainers. This keeps the entry cost low for plugin maintainers. Hmmm No. Do users remember that the have to do regularly git submodules update? Note that a plugin that fails to meet quality requirements, or some other criteria for inclusion in the combined release, still has its own repository available to users. So plugins can be added or dropped from the combined release whilst still being available to users from their individual repository, providing item 4. This can be solved by deactivating the plugin in general build flavor by setting the autotools and waf parameters to Don't build. If user want to have, they could use --enable Cheers, Frank signature.asc Description: OpenPGP digital signature ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] Plugin : Geanyprj
Am 24.11.2011 17:23, schrieb Johann SAUNIER: Thanks a lot for your reactivity ! my answers and questions below : 2011/11/23 Frank Lanitz fr...@frank.uvena.de mailto:fr...@frank.uvena.de 2) I tried ./waf updatepo and the results are big changes in .po files, like if they were all much out of date - do we have to use updatepo each time we add a translatable string or should we add it by hand in the .po file of our native language (and the other ones we know how to translate) ? Well, No. The po files are only generated on demand as it will generate a lot of overhead due the changes e.g. on line numbers. Please don't add strings manual to po-files unless you are 110% sure what you are doing. So what should I do ? 1) ask a maintainer to run ./waf updatepo on geany-plugins, update my working copy when it is done and create my patch that will contain only the strings I added 2) run ./waf updatepo myself and send the patch with the lot of updates (even on plugins I don't work on) Usually we have a language orientated view on translations rather than updating for each plugin as geany-plugins is a combined project. From time to time it makes sense to translate it plugin by plugin, but this is up to the translator. In your cause I'm not sure, whats the bast way. I think just sending an updated po-file for your language Cheers, Frank ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
[Geany-devel] Geanyprj-Crash (was: Re: Plugin : Geanyprj)
Am 23.11.2011 16:01, schrieb Johann SAUNIER: 1) In a previous post, Lex told me that he couldn't create a new project because of a crash : Unfortunately compiled against Geany Git it crashes creating a new project. I don't have time (or interest I admit) to find out why, but it may need some maintenance. Cheers Lex I can't reproduce this crash as everything works perfectly on my machine. I build against : - https://geany-plugins.svn.sourceforge.net/svnroot/geany-plugins/trunk/geany-plugins and - branch 'master' of git://github.com/geany/geany http://github.com/geany/geany Am I wrong ? I guess the best would be to have Lex provide a backtrace here. Maybe its related to some compiler magic or architecture based (e.g. 32bit pointer vs 64bit pointer vs integer) Cheers, Frank ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
[Geany-devel] README.waf-issue (was: Re: Plugin : Geanyprj)
Am 24.11.2011 17:23, schrieb Johann SAUNIER: 3) by executing step 2, I noticed an error in the README. waf. Do I have to send a patch or just tell it to a maintainer on this list ? What's the issue you did found? There a bunch of ppl having access to this file and therefor can update it the issue is that the command to update po files is ./waf updatepo instead of ./waf --update-po Fixed ;) Thanks. Cheers, Frank ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
