On 25 March 2014 07:53, Frank Lanitz frank@frank.uvena.de wrote:

On Mon, 24 Mar 2014 13:42:15 -0700 Shankhoneer Chakrovarty shankhoneer@gmail.com wrote:

...

Hi,

As per the last discussion ( email subject: Hi! ) I started looking at the geany-plugin project. I found the following plugins orphaned:

1. codenav
2. geanylua
3. pretty-printer
4. shiftcolumn

All these plugins are still alive (I think).

I was not able to build geany-plugin as the configure expects geany version to be 1.24. I have geany version 1.23 installed in ubuntu. Can somebody please help me to install the geany-plugin? I have cloned geany and geany-plugin directory.

You will need to start to build recent Geany from git. This can be done via ./autogen.sh (from git ..), make sudo make install -- or using waf ./waf configure && ./waf build && sudo ./waf install

NO, don't do this for development (sorry Frank :)

Don't overwrite your system geany with a development version, if it breaks you may not be able to edit it to fix it (without using say gedit :). That applies even more to plugins.

Cheers lex

After that you can start building the plugins. You might need to adjust the path to make geany-plugins find your geany 1.24 (or just deinstall the geany 1.23.1 package from ubuntu ;) ) However -- compiling the plugins can be done in the same manner.

Cheers, Frank

---

Devel mailing list Devel@lists.geany.org https://lists.geany.org/cgi-bin/mailman/listinfo/devel

Thanks Frank and Lex, I was able to compile and make geany-plugin. Can you please help me to identify which plugins has already been ported to gtk3 and which not? What exactly are we trying to do by porting the plugins to gtk3?

Thanks, Shankhoneer Chakrovarty

On Mon, Mar 24, 2014 at 2:08 PM, Frank Lanitz frank@frank.uvena.de wrote:

On Tue, 25 Mar 2014 08:00:20 +1100 Lex Trotman elextr@gmail.com wrote:

...

...

You will need to start to build recent Geany from git. This can be done via ./autogen.sh (from git ..), make sudo make install -- or using waf ./waf configure && ./waf build && sudo ./waf install

NO, don't do this for development (sorry Frank :)

Don't overwrite your system geany with a development version, if it breaks you may not be able to edit it to fix it (without using say gedit :). That applies even more to plugins.

Well... yes. You are true. Just had in mind to get a working devel version running -- in the fast way. The better way of course to leave system's geany on the box and install devel geany to some other path and ensure, paths are set correctly on configure run.

Cheers, Frank

---

Devel mailing list Devel@lists.geany.org https://lists.geany.org/cgi-bin/mailman/listinfo/devel

Thanks Lex.

Means the plugin can be built for use with a version of Geany that is built for gtk3, as well as for a version of geany built for use with gtk2.

What that means needs to be changed in the plugin is specific to the plugin, if it was known it probably would have been done already, thats what you need to figure out to port them.

Now I know :) . So all I have to do is build all the orphaned geany-plugin and see if their build is ok and test them individually so that they dont break in geany 1.24 (the latest from git). For time being I can take the ownership of the orphaned geany-plugins that I mentioned in the first mail, in that case do I have to modify the MAINTAINERS file and add my name and email id to it?

Thanks, Shankhoneer Chakrovarty

Hi Shankhoneer,

I've started to work on codenav plugin one week ago :)

(OFFTOPIC: can someone check my PR and says me if I'm doing right or not? ;))

On Mon, Mar 24, 2014 at 10:58 PM, Shankhoneer Chakrovarty < shankhoneer@gmail.com> wrote:

Thanks Lex.

...

Means the plugin can be built for use with a version of Geany that is built for gtk3, as well as for a version of geany built for use with gtk2.

What that means needs to be changed in the plugin is specific to the plugin, if it was known it probably would have been done already, thats what you need to figure out to port them.

Now I know :) . So all I have to do is build all the orphaned geany-plugin and see if their build is ok and test them individually so that they dont break in geany 1.24 (the latest from git). For time being I can take the ownership of the orphaned geany-plugins that I mentioned in the first mail, in that case do I have to modify the MAINTAINERS file and add my name and email id to it?

Thanks, Shankhoneer Chakrovarty

---

Devel mailing list Devel@lists.geany.org https://lists.geany.org/cgi-bin/mailman/listinfo/devel

On 25 March 2014 11:48, Shankhoneer Chakrovarty shankhoneer@gmail.com wrote:

Hi Frederico,

...

I've started to work on codenav plugin one week ago :)

Can you please update the MAINTAINERS file?

Only update the MAINTAINERS file if you are offering to take over maintainership of the plugin, that means you are offering to answer questions about the plugin on ML and to fix bug reports on the plugin and generally improve the quality of the plugin.

You can still provide patches/pull requests without maintainership.

Cheers Lex

So the process as I understand is, fork the geany-plugin project, update the maintainers file which is updating the Status, P,M and W of codenav,push the changes and drop a mail to Frank who will merge.

Thanks, Shankhoneer Chakrovarty

---

Devel mailing list Devel@lists.geany.org https://lists.geany.org/cgi-bin/mailman/listinfo/devel

On Tue, 25 Mar 2014 09:30:42 +0100 Federico Reghenzani federico.dev@reghe.net wrote:

Yes, no problem, I thought that I could not auto-add me to MANTAINERS file, but if I can, I'm happy to contribute maintaining that plugin.

I'll send the email to Frank soon :)

Applied. And now, time to get some things done ;)

Cheers, Frank