Devel September 2011

devel@lists.geany.org

18 participants
38 discussions

Re: [Geany-devel] SF.net SVN: geany:[5909] trunk/src/utils.c
by Lex Trotman 16 Sep '11

16 Sep '11

On 12 September 2011 03:06, <colombanw(a)users.sourceforge.net> wrote: > Revision: 5909 > http://geany.svn.sourceforge.net/geany/?rev=5909&view=rev > Author: colombanw > Date: 2011-09-11 17:06:11 +0000 (Sun, 11 Sep 2011) > Log Message: > ----------- > Cleanup code in utils_open_browser() > > Modified Paths: > -------------- > trunk/src/utils.c > > Modified: trunk/src/utils.c > =================================================================== > --- trunk/src/utils.c 2011-09-02 21:45:20 UTC (rev 5908) > +++ trunk/src/utils.c 2011-09-11 17:06:11 UTC (rev 5909) > @@ -81,37 +81,28 @@ > cmdline = g_strconcat(tool_prefs.browser_cmd, " \"", uri, "\"", NULL); > if (! g_spawn_command_line_async(cmdline, NULL)) > { > + static const gchar *browsers[] = > + { > + "xdg-open", > + "firefox", > + "mozilla", > + "opera", > + "konqueror", > + "netscape" Hi Colomban, What about adding chrome? Cheers Lex

6 19

Re: [Geany-devel] SF.net SVN: geany:[5917] trunk/NEWS
by Matthew Brush 16 Sep '11

16 Sep '11

On 09/14/2011 07:38 AM, ntrel(a)users.sourceforge.net wrote: > ----------- > Add ntrel's changes for 0.21. > [...] > + > + Editor > + * Update Scintilla to version 2.22. Wasn't it updated to 2.25? Cheers, Matthew Brush

4 4

Adding size_t before release
by Matthew Brush 15 Sep '11

15 Sep '11

Hi, I don't know who generates the c99.tags, but it would be cool if the next release of Geany had the `size_t` symbol in its default tags. I can't get Geany to parse my GNU headers using create_c_tags.sh script (or otherwise), but even just copying the line for `ssize_t` and dropping the first S works well enough to get auto-completion and highlighting of this symbol. Cheers, Matthew Brush

4 8

Re: [Geany-devel] SF.net SVN: geany:[5915] trunk/TODO
by Lex Trotman 15 Sep '11

15 Sep '11

Hi Nick, [...] > + o asynchronous build commands on Windows > + o (filetype-independent run command & keybinding) This only needs a GUI, you can already put filetype independent run commands in both geany.conf and project files in the [build-menu] section like: EX_01_LB=Run command label EX_01_CM=./whatever EX_01_WD=%p/bin Keybindings need to be for all extra commands, filetype and filetype independent ones, not just the exe one. Probably the whole build keybinding group needs to be made dynamically like plugin groups are so the size can be determined at runtime? Cheers Lex

2 2

GeanyPy Keybindings Again
by Matthew Brush 13 Sep '11

13 Sep '11

Hi, I started working on keybindings again for GeanyPy and I was hoping to get a little advice from the experts. I've hacked together some code that allows the single GeanyPy plugin to create new GeanyPlugin structs so that it can add multiple keygroups for the single plugin. This actually seems to work fairly well considering how kludgey the implementation is (ie. copying structs from Geanys code into GeanyPy's code because they aren't exposed, etc.). Now I have two remaining challenges to overcome. The first is that there doesn't seem to be a way to remove/delete a keygroup, that is to undo what plugin_set_keygroup does. The function I think I need is keybindings_free_group(), but it's not in the plugin API, and I can't "fake" it like I've done with other parts since it requires the `keybinding_groups`. So basically what's happening, is when a Python plugin is unloaded and is cleaned up, I free the "sub" GeanyPlugin and all it's memory. Now when you go into the Preferences->Keybindings you see just weird things where the plugin name/keybindings were, presumably since Geany is reading from freed/adjacent memory or some such. So the first question is, is there a way to remove a plugin/keygroup from those registered with Geany? At this point, I don't really care if it's a kludgey solution, I just want it working :) The second challenge I'm facing is coming up with a way for GeanyPy to manage connection of Python plugins keybindings and dispatching to them when a keybinding is pressed. What I've done so far is, as mentioned above, to create a phony GeanyPlugin/GeanyKeygroup for each plugin, and each plugin gets allotted KEYBINDINGS_MAX bindings using the plugin_set_keygroup() function. The problem I'm having now is how to associate the Python plugin (consider it a C struct if it helps) with the keybinding. It seems like it would be easier if there was possibility of passing a closure or whatever it's called when connecting to the key binding, but GeanyKeyCallback doesn't seem to support this. I've a tried and failed so far with a few different ideas. So, can anyone recommend a decent way of mapping which Python plugin connected to which keybinding and then call out to the plugin when the keybinding is activated? One last thing since I'm already writing a really long email, I notice in keybindings.h[1] in the GeanyKeyGroup definition, there's a 'plugin' member that is mentioned elsewhere in keybindings.c (I think) as being used by GeanyLua or some such. What is this for, and would it be useful for what I'm trying to do with GeanyPy? Also, why is the comment above the definition "Plugins should not set these fields", while the comment for the 'plugin' member says "Used by plugins"? [1] http://git.geany.org/geany/tree/src/keybindings.h#n58 Apologies for the really long message, but I'm at a bit of a loss (yet again). Cheers, Matthew Brush

3 4

Why Geany doesn't use exactly what is set in "marker_search"?
by Jean-Philippe Fleury 12 Sep '11

12 Sep '11

Hi, I noticed that the background color really used in Geany to mark searches is never the exact color set in "marker_search" in color schemes, as if a kind of translucency was automatically applied. For example, see the following screenshot: http://www.jpfleury.net/depot-fichiers/png/geany-themes-gedit-cpp.png The second color scheme sets: marker_line=0x000000;0xffff00 marker_search=marker_line but we see in the screenshot that Geany really uses color "0xffffc3" (washed yellow) instead of "0xffff00" (bright yellow). Same thing happens with any color scheme. I tried to play with "marker_translucency", but it doesn't change anything. Do you have any idea why this happens? Regards, Jean-Philippe

4 14

Re: [Geany-devel] SF.net SVN: geany:[5909] trunk/src/utils.c
by Thomas Martitz 12 Sep '11

12 Sep '11

Bringing this back to geany-devel. Am 12.09.2011 11:23, schrieb Lex Trotman: > Hi Thomas, > > [...] >> Yes, and calling Firefox Firefox is one of the reasons for those distros to >> fork debian :) >> >> Since iceweasel is a pure debian thing, it should perhaps the responsibility >> of the debian package maintainer to add iceweasel. > Then we should add this to the distro packaging instructions and tell > them where to change the hardcoded tools prefs default as well. > >>> Given the rate bugs get found in browsers I wouldn't want to >>> unexpectedly run an old un-updated browser, thats a real risk. >> I think that's a bit exaggerated. > So you are happy to keep using the compromised CAs then, since updates > only just removed them? Gee, I've got just the web page for you to > type your banking details into ;-) > No, but this is not Geany's concern. Best regards.

2 1

Include geany-themes before release?
by Matthew Brush 03 Sep '11

03 Sep '11

Hi, Should we add (parts of) the geany-themes[1] project to Geany before the release freeze for 0.21? If so, I propose that we add all the filedefs, the alt.conf theme, one light theme, and one dark theme. If nobody is opposed, I will prepare a patch in short order. P.S. I just added some info about geany-themes on the colour schemes section of the wiki[2]. [1] https://github.com/codebrainz/geany-themes [2] https://wiki.geany.org/themes/start Cheers, Matthew Brush

3 2

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

Devel September 2011