Devel May 2011

devel@lists.geany.org

17 participants
39 discussions

Fix crash and memory leak in treeviewer.c.
by Thomas Martitz 12 May '11

12 May '11

In path_is_in_dir(), if it's about to return NULL (if the function parameters have no path components in common) it tried to free() a string literal, which causes a crash. In the same function, there was a memory leak, because diffed_path was reassigned without being free()'d before. Fix both problems.

2 5

TextMate Themes for Geany
by Maciej Ciemborowicz 12 May '11

12 May '11

Hi again, I'm still working on Textmate to Geany color schemes conversion and I like to show you some effects. I also want to ask you for help and contribution, because at this stage, work is more time consuming and arduous. Here is a converter written in Ruby. This is a Geany theme writer's module, only this file is necessary for you: https://github.com/ciembor/coloration/blob/master/lib/coloration/writers/ge… As you can see, there are mappings of TextMate properties in format: "geany_property" => @items["some_property"] || @items["alternative_property"] || @items["etc"] || "emergency_geany_property" And here are some (over 250:)) TextMate themes with equivalents for Geany: https://github.com/ciembor/TextMate-Themes https://github.com/ciembor/geany-themes/tree/master/colorschemes But it's not easy to find accurate properties in TextMate. I didn't found any documentation. Worse still, I have no Mac :D. The only way is to read theme after theme, try new mappings and compare them with screenshots: http://textmatetheme.com/ Any remarks are welcome. You may put them on this mailing list or here: https://github.com/ciembor/coloration/issues Cheers - Maciej Ciemborowicz P.S. One more thing. Some properties, like colors of line numbering are not existing in any TextMate theme :(. I still consider the best solution.

2 2

Git Switch (again)
by Matthew Brush 11 May '11

11 May '11

Hi, I'd like to revive this thread[1]. I wasn't around during the initial thread but Jiri has just pointed me to it and I read it through. I'd like to summarize (at least my take) on that thread and then list some pros and cons to stimulate a discussion. Disclaimer: I am not an expert on anything, but I've used both Subversion (via SourceForge and Google Projects) and Git (via GitHub.com and Gitorious). Also, this is as much about not using SourceForge as it is about switching away from Subversion. Summary from previous thread: The people in the thread who do not want to switch to Git, or those who don't seem to care either way, are those who have commit access to Subversion on SourceForge. Most (if not all) contributors to Geany are using Git (via git-svn). The workflow for those who don't have commit access on the subversion repository, when contributing to Geany is sub-optimal (to put it politely). SourceForge is painfully slow and the interface for viewing SVN source code online isn't great. I think the reason GitHub/Gitorious is mentioned so much is not only because of the "Git" in their name, but also because it allows people who don't have commit access to actually be active members in the community, by means of having their public forked repositories, sending merge/pull requests, etc. Cons from the previous thread: - It's more social - Not plain enough (I guess too Web 2.0/feature-full/cluttered) - Effort required to move the project - Having to learn a new VCS for those not familiar with Git Pros from the thread: - It's more social - It's not so plain (ie. has more features which work well). - Moving the codebase and history is very easy, for example using the script from the thread or GitHub offers you to import a SVN repository through the web interface when creating a new repository. - Easier to contribute to the project for those without write access - Faster hosting and better interface. - Harder to have patches slip through the crack. - Not having to maintain/create patches as much/at all. - Public contributor repositories associated with the main one. - No need to maintain changelog and authors files - Proper attribution, blame and history for contributors and not having to put "Thanks" in all the commit messages. Not sure if I missed any, or misconstrued them. Here's some features of better project hosting sites. I'm listing things from GitHub because I know it better than Gitorious and others: - Great source code viewer, branch/file browser, history/commit viewer. - Ability to link to and comment on commits and even specific lines of a commit, for code review, etc. - Nice network graph viewer to get a better idea of what everyone else is working on, needs to be commited, etc[2]. - Tracker for pull/merge requests so no need for contributors to generate/maintain patch(sets) and keep bumping ML threads so their patches don't go forgotten. - Fork queue to compare other peoples repositories' commits against your repository to cherry pick specific commits, with an indication of whether or not the commit/patch will likely cleanly apply - Good issue/bug tracker - Built-in Wiki software - Nice graphs to show languages, impact, commit activity, etc - Web hooks to notify by email/ML, IRC and other services of commits, etc.[4] - No need to create nightly tarballs separately since the server takes care of this automatically when users clicks the Download link. Hopefully this will stir up a little discussion about actually switching because every time I use SourceForge I die a little inside :) I think switching to one of the Git project hosting sites will really help the community/contributors get involved and feel like part of the team while still making sure the official code is controlled by a great team of core developers. Obviously I'm not suggesting that the SourceForge project page is deleted, just switching the main development activity to elsewhere. We could have a git/svn mirror over at SourceForge still, and even keep their bug/feature tracker, though I can't see why, since it's pretty lousy. It really wouldn't be hard either, the whole "switch" be done in probably 10-15 minutes, maybe 1-2hrs to wait for the history to be imported. There's no real reason it needs to be a big deal either, we could test out another project site and keep it the way it currently is still with not much extra effort, just someone/somescript needs to push to the new project page after committing to SVN. Basically all it would take beyond that is for one of the founders/core members to take some time to setup an account and push the code. I already have a Geany repository[5] I use over at GitHub.com if you want to play with it to test out that site. Also, Jiri has an old repository[6] on Gitorious. Neither are exactly up to date. It's fun also to see the Geany hackery already happening on these sites[7][8]. Sorry again for the long message. Cheers, Matthew Brush [1] http://lists.uvena.de/geany-devel/2010-June/002602.html [2] https://github.com/blog/39-say-hello-to-the-network-graph-visualizer [3] https://github.com/blog/270-the-fork-queue [4] https://github.com/github/github-services [5] https://github.com/codebrainz/geany [6] http://gitorious.org/geany/complete [7] https://github.com/search?langOverride=&q=geany&repo=&start_value=1&type=Re… [8] http://gitorious.org/search?q=geany

7 32

SplitWindow Windows support/fixes (was: Re: Geany-Newsletter issues #2 reaching target line)
by Enrico Tröger 10 May '11

10 May '11

On Thu, 05 May 2011 07:45:43 -0700, Matthew wrote: >On 05/05/11 02:11, Frank Lanitz wrote: > >> My understanding was that this has been fixed and now is working >> also on Windows. What is pending here? > >I don't think it ever got fixed/applied. Last I remember, Enrico said >he will do in the next few days, and then I never heard anything more. I'm so sorry (honestly). I didn't intend to forget it... >What's pending is the patch to fix the original Windows bug[1][2] and >re-enabling the Split Window plugin for Windows build[3][4]. > >[1] http://git.geany.org/geany/tree/plugins/splitwindow.c#n310 >[2] http://git.geany.org/geany/tree/plugins/splitwindow.c#n361 >[3] http://git.geany.org/geany/tree/plugins/makefile.win32#n61 >[4] http://git.geany.org/geany/tree/wscript#n355 Do you still have links to the patches for [1] and [2]? I feel a bit lost as we had a couple of different patches and approaches, IIRC. This is obviously my fault because I delayed it that long, sorry again. Though I hope you can assist me with the patches a bit before I commit the wrong one and we start from the beginning. [3] and [4] are trivial enough. Regards, Enrico -- Get my GPG key from http://www.uvena.de/pub.asc

5 9

[RFC] Plugin Template
by Matthew Brush 10 May '11

10 May '11

Hi, I was thinking it would be useful to have a template directory with all the "boiler-plate" for a Geany plugin under version control to get people started quicker writing a new plugin that could become part of the Geany Plugins project easier. I saw something similar[1] in the GStreamer project. My ideas was to put in the directory the files required for the build system(s), a generic README template, a GPL2 COPYING, etc, and a src/ dir with a basic demo plugin (maybe from the Geany plugins/ dir?). What other common files besides these should be in there? AUTHORS COPYING ChangeLog Makefile.am NEWS README THANKS TODO wscript_build wscript_configure (are both these Waf files needed?) ../build/foo.m4 (how to include if it's in .. ?) src/foo.c src/Makefile.am configure.ac? (for building before it's in Geany Plugins proper) What do you guys think? Is it worthwhile? Have I missed any important files? I was going to follow this up with a tutorial on the Wiki explaining how to check-out the template, describe which files needed to be modified and how to do so, etc. Also it would have some more general notes from HACKING, getting commit access, the cppcheck stuff and so on. This would be a good companion to the plugin howto I think. I was also thinking about doing a similar template/tutorial for a Vala plugin. Feedback would be appreciated. Cheers, Matthew Brush [1] http://gstreamer.freedesktop.org/data/doc/gstreamer/head/pwg/html/chapter-b…

4 5

Geany-Newsletter issues #2 reaching target line
by Frank Lanitz 10 May '11

10 May '11

Hi folks, About two month ago we released issues 1 of Geany newsletter and we are thinking of doing a new one upcoming week. Not all work is done yet, some contents are missing (mea culpa e.g. some parts I wanted to write) as well as some optical corrections needs to be done on both, HTML and PDF version of the newsletter. However, if you like to contribute some content or some patch for buildsystem, CSS and other templates for issue 2 -- now its a good time to let us know ;) You will find current 'devel' version at http://git.geany.org/newsletter/tree/ Cheers, Frank

5 13

hex mode
by Liviu Andronic 10 May '11

10 May '11

Hello Does Geany have a hex mode, that is can I open files in hex mode? And a bit more OT, Geany refuses to force-open a PDF file. Nano, for example, opens the PDF. Is it normal? Regards Liviu -- Do you know how to read? http://www.alienetworks.com/srtest.cfm http://goodies.xfce.org/projects/applications/xfce4-dict#speed-reader Do you know how to write? http://garbl.home.comcast.net/~garbl/stylemanual/e.htm#e-mail

7 11

Planning bugfix release 0.20.1
by Enrico Tröger 09 May '11

09 May '11

Hi, I'd say let's make a 0.20.1 bugfix release soon. So we can release the fixes made since the 0.20 release for users. If no one beats me by time, I'll create a 0.20.1 branch based on the 0.20 tag on Sunday and then we can backport relevant fixes. Regards, Enrico -- Get my GPG key from http://www.uvena.de/pub.asc

4 7

SVN Log Stats
by Matthew Brush 08 May '11

08 May '11

Hi, I was curious about the statistics for the Geany project so I hacked together some Python code to peel out some values from the SVN log. If anyone cares, the following are some of what I found: Total commits: eht16: 2466 ntrel: 2182 frlan: 413 colombanw: 87 kretek: 74 elextr: 18 peterscholtens: 9 dmaphy: 8 clytie: 2 Total lines changed: ntrel: 6195 eht16: 4174 frlan: 455 colombanw: 326 kretek: 103 elextr: 34 dmaphy: 9 peterscholtens: 9 clytie: 4 Since the log doesn't attribute patch authors normally, I was going to try and parse the "Thanks, Foo bar" messages to get counts for read-only developers from the commit messages, but it's too much trouble. If anyone is curious, the word 'thanks' occurs 410 times in the log. Anyway, I thought others might be interested to see these numbers, since I couldn't find them through SF/otherwise. Happy Coding, Matthew Brush

4 9

Project close problem
by Lex Trotman 08 May '11

08 May '11

Hi All, On 0.20 Linux I have noticed a problem when closing a project, occasionally instead of going back to the files that were open, the project files stay open and become the non-project open file set. I have only seen it a couple of times and havn't been able to find a way of producing the problem reliably. Has anyone else seen it or have any ideas? Cheers Lex

3 3

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

Devel May 2011