Devel June 2011

devel@lists.geany.org

10 participants
20 discussions

Patches for review
by Jiří Techet 08 Oct '12

08 Oct '12

Hi, I'm sending my stack of patches against geany again, this time as individual patches. Here's the full list: [PATCH 01/19] Prevent -Wmissing-prototypes report warning when compiling a plugin [PATCH 02/19] Add signals for project options dialog opening and closing [PATCH 03/19] Make the project menu accessible by plugins [PATCH 04/19] Make it possible to change project patterns by plugins [PATCH 05/19] Don't be annoying when not necessary [PATCH 06/19] Make it possible for plugins to change the base directory of msgwindow [PATCH 07/19] Open the file in the msgwindow even if no linenumber is specified [PATCH 08/19] When closing tab, return to the document at the top of the MRU list [PATCH 09/19] Use wider entry for project file path [PATCH 10/19] New utils function to get relative path from one directory to another [PATCH 11/19] File name in the project settings dialog shouldn't look it is editable [PATCH 12/19] Use relative paths in the project files [PATCH 13/19] Remove the "set" button from the project properties dialog [PATCH 14/19] Rewrite tab switching queue [PATCH 15/19] Do not insert --include= when the search pattern entry is empty [PATCH 16/19] Use project patterns in the FIF dialog [PATCH 17/19] Make the tab switching dialog a bit more useful [PATCH 18/19] Use standard include paths for "open selected file" [PATCH 19/19] Use per document indent sizes Only some of them are required by gproject - others are just suggestions for improvements. I didn't explicitly distinguish between these two types of patches but it should be pretty clear from the description. There have been some minor changes since my last post - mainly the change of the FIF dialog to contain combo box for pattern selection and there are also some new patches - the detailed description is in the individual emails. Of course many of the patches are suggestions only so further discussion is welcome. Cheers, Jiri

8 68

Status of SM-Branch
by Frank Lanitz 31 Mar '12

31 Mar '12

Hi folks, I saw that the SM-branch is merged with trunk on a regular basis, but not sure what's the current status of that branch. Can someone help me out there? Cheers, Frank -- http://frank.uvena.de/en/

2 4

Re: [Geany-devel] Indentation using regex (was [PATCH 14/19] Rewrite tab switching queue)
by Jiří Techet 07 Dec '11

07 Dec '11

On Thu, Sep 16, 2010 at 19:27, Thomas Martitz <thomas.martitz(a)student.htw-berlin.de> wrote: > On 16.09.2010 02:23, Lex Trotman wrote: >> >> Hi Jiri, >> >> I couldn't get this to work at all, it printed "calling indent this >> line" all the time but didn't indent :-( >> >> I only had half an hour so I couldn't investigate much. >> > > I have the same experience. Auto-indentation doesn't seem to work anymore > (e.g. when hitting enter after on a line that ends with {, or when typing > }). I have just re-tested it again and it works on my machine (I have forgotten one trace in the code - that's what you see in the console). A quick question: have you read the commit log? This patch makes it possible to specify several regex patterns for every filetype which determine under what condition the indentation is performed. The pattern variables are specified under the [settings] section of the given filetype and their value is the regex to be used. The variables are as follows: * indent_this_line_regex - the match is performed after every keystroke and if the regex matches, the indentation is performed on the current line * indent_next_line_regex - the match is performed only when enter is pressed. The indentation is applied on the next line * unindent_this_line_regex - like indent_this_line_regex but unindents instead * unindent_next_line_regex - like indent_next_line_regex but indents instead Comments and strings are detected from the lexer so these can be ignored inside the patterns. For instance these are very basic rules for GNU indent style: indent_next_line_regex=^.*\\{[[:blank:]]*$ unindent_this_line_regex=^[[:blank:]]*\\}$ indent_this_line_regex=^[[:blank:]]+\\{$ unindent_next_line_regex=^[[:blank:]]*\\}[[:blank:]]*$ By commenting-out the last two lines you get ANSI indentation style. If you replace \\{ and \\} with begin and end, respectively, you get analogous rules for pascal. Notice the double-escaping of { and } - the first escape sequence is for the keyfile ini format (so for the regex itself \\ becomes \). This means that in order to make it work e.g. for C, you have to edit ~/.config/geany/filedefs/filetypes.c (or the corresponding file under /usr/local/share/geany) and add indent_next_line_regex=^.*\\{[[:blank:]]*$ unindent_this_line_regex=^[[:blank:]]*\\}$ indent_this_line_regex=^[[:blank:]]+\\{$ unindent_next_line_regex=^[[:blank:]]*\\}[[:blank:]]*$ under the [settings] section (+ restart geany). Please let me know if it works (but also in the opposite case ;-). Jiri > > Best regards. > _______________________________________________ > Geany-devel mailing list > Geany-devel(a)uvena.de > http://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel >

6 35

Newsletter: Markuplangauge
by Frank Lanitz 16 Jul '11

16 Jul '11

Hi, You might have recognized that there have been a discussion on which markuplangauge/technique we will use for future Geany newsletter to write and create PDF/HTML/other output formats in. During this discussion a lot of different languages and ways have been suggested so decision is not easy. However, we (well, I) decided to do it on a more democratic way by doing a poll about. But before we are doing this poll we need to collect all possible ideas and put some basic facts together. To do so I did create a wiki page (please don't care about the theme for the moment as this is under discussion inside another thread) at http://wiki.geany.org/newsletter/markuplanguages where I like to ask everybody to enter suggestions based on a minimal feature list I put together you can also find at this page. Based on that list I will create a poll upcoming weekend (around June, 4th) - I will announce tis inside another mail with some basic rules. Cheers, Frank

2 5

Changed file saving implementation for systems with GIO
by Nick Treleaven 30 Jun '11

30 Jun '11

Hi list, To workaround bug(s) in GVFS, I've now changed the file saving implementation for systems with GIO in SVN trunk. See also: http://lists.uvena.de/geany-devel/2010-November/003412.html Please help test this. File permissions should be preserved after saving, and disk space exhaustion should now be handled without losing the previously saved file. Also, running geany --version (or -V) should now also show 'GIO' if your system has it and Geany knew about it at build time. Begin forwarded message: Date: Tue, 02 Nov 2010 17:42:54 +0000 From: ntrel(a)users.sourceforge.net To: geany-commits(a)uvena.de Subject: SF.net SVN: geany:[5361] trunk Revision: 5361 http://geany.svn.sourceforge.net/geany/?rev=5361&view=rev Author: ntrel Date: 2010-11-02 17:42:54 +0000 (Tue, 02 Nov 2010) Log Message: ----------- Use g_file_replace_contents() if available to save documents - this should help workaround bugs in GVFS. Needs testing. Nick

7 67

various prefs - statusbar_template
by Dimitar Zhekov 24 Jun '11

24 Jun '11

Hi, There is a small problem with the various/hidden preferences editor, namely with the statusbar_template default value. The options are: 1. Display/edit an empty default value. Requires no changes in Geany, but is not very convenient: you must read the documentation and find the default for your language, probably in the .po files. Well you must do that currently for if editing the [empty] value in geany.conf. 2. Display/edit the real default value. Requires minimal changes, currently implemented in the various editor patch, but that value will be saved in geany.conf, even without being edited. So if the LANG is changed, the old value will still be used, and you'll have to open Edit -> Preferences -> Various, right-click statusbar_template and choose Reset. Hopefully the LANG changes will be rare. 3. Display/edit the real default value, but save it as empty if it matches the default. Convinient, but requires several hacks, especially if the editor will support right-click and Reset to default. RFC. I'm against option 3. -- E-gards: Jimmy

3 2

Geany-Plugins: Updated POTFILES.in
by Frank Lanitz 22 Jun '11

22 Jun '11

Hi folks, I've updated the POTFILES.in for combined Geany-Plugins project based on output of find ./ -name "*.c". I kept the .h files which have been already be inside the list but would like to ask pliugin developers to double check whether all important files which might contain translatable strings are inside the list. Cheers, Frank -- Frank Lanitz <frank(a)frank.uvena.de>

1 0

GIO saving made configurable?
by Colomban Wendling 20 Jun '11

20 Jun '11

Hi, During the phase of removing code that is not relevant anymore since the dependency bump, I fatally came out to write_data_to_disk(). Now we can assume we have GIO, it may seem sensible to drop completely the C API file saving code... ...However, GIO saving seems to cause some problems on some complex situations: https://sourceforge.net/tracker/?func=detail&atid=787791&aid=3220784&group_… https://sourceforge.net/tracker/index.php?func=detail&aid=3184594&group_id=… https://sourceforge.net/tracker/index.php?func=detail&aid=3126535&group_id=… (and maybe more -- at least one on IRC). So I'm wondering: do we really want to drop the C API-using code path, or do we want to make it configurable (like safe file saving)? Well, since I'm not completely sure of what causes the problems and what are the downsides (either I don't remember or I did not participate to the discussion...), I prefer to ask you what do you think/know/remember/whatever about this. I join a sample patch that make GIO saving configurable (just like safe file saving) with it enabled by default, if anybody wants to check it out. So, what's your opinion? Cheers, Colomban

4 7

Re: [Geany-devel] SF.net SVN: geany-plugins:[2096] trunk/geany-plugins/gproject/src/ gproject-project.c
by Frank Lanitz 20 Jun '11

20 Jun '11

Hi folks, On Sun, 19 Jun 2011 22:30:57 +0000 techet(a)users.sourceforge.net wrote: > -#include <geanyplugin.h> > +#include <geany/geanyplugin.h> I'm not 100% sure, but is this really correct? Cheers, Frank -- http://frank.uvena.de/en/

2 1

Plugins: Bump dependencies also to GTK 2.12 / GLIB 2.16?
by Frank Lanitz 20 Jun '11

20 Jun '11

Hi developers, As currently the dependencies for Geany are getting bumped to GTK 2.12 and GLIB 2.16 I'm wondering whether we should also bump dependencies of current devel version of geany-plugins to Geany 0.21 and with this step also to this versions of GTK/glib? Cheers, Frank -- http://frank.uvena.de/en/

3 3

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

Devel June 2011