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
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
>
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
Hi,
any objections in increasing the GTK minimum requirement of Geany to
GTK 2.12 (and GLib 2.16)?
This would make quite some code obsolete and so could be removed.
Also, it would make it easier to migrate to using Glade 3 with
GtkBuilder instead of Glade 2 (and in the long term makes getting
compatible with GTK3 easier, but really, later :D). Though I'd like to
do this step some time later. Also we could rely on GIO which came with
GLib 2.16 which should remove some #ifdefs.
I think the current minimum of GTK 2.8 can be increased as GTK 2.12 is
already about three years old already.
Any objections?
Regards,
Enrico
--
Get my GPG key from http://www.uvena.de/pub.asc
Hi,
I generated tags for all of the Vala .vapi files on my system. If you
want to add them to the contrib section, feel free. Maybe there should
be a subdirectory for Vala tags since theres 135 different tag files. I
put them up at:
https://github.com/codebrainz/geany-vala-tags/tree/master/tags
(To get them all at once, use the "Downloads" button)
Also, should there be a set of default tags for Vala as there are for
other languages (php, python, etc)? I've included a separate vala.tags
that combines tags for vala-0.10 and glib-2.0, which could be included
as a default. It is here:
https://github.com/codebrainz/geany-vala-tags/raw/master/vala.tags
Note: loading all 135 tags at once locks up Geany's UI for over 2 second
on my computer :)
Cheers,
Matthew Brush (codebrainz)
Hi.
When "Escape sequences" checkbox is checked in Find or Replace dialog,
before escaping the find and replace strings we should save the
original ones, so that they can be used in messages shown to user and in
the history of those dialogs' entries. This is what the patch is about.
I described in the commit message (see the top of the patch) the changes
made in the code. Just in case, here is a copy:
In the code, now we pass the original text together with the one
that is actually searched for. New `original_text' field was added to
GeanySearchData. A bug was fixed in document.c:show_replace_summary():
it did not escape the "No matches found for ..." string.
Hope that I did not touch plugin API with these changes. In header
files I changed the following:
- document_find_text()'s signature
- document_replace_text()'s signature
- search_find_usage()'s signature
- struct GeanySearchData
--
Best regards,
Eugene.
Hi,
I started working on support for reading Exuberant Ctags files. The
commit message sums up most of the details I hope. If anyone wants to
try it out and/or review the code, that would be much appreciated.
The relevant commit is here on my 'ctags-support' branch:
https://github.com/codebrainz/geany/commit/a642077c47ea444e9b13b9d2ad244be0…
Or the attached patch has the same information.
I haven't tested a whole lot but it seems to be working well, allowing
colourizing of the tags and auto-completion. It doesn't (yet) get the
arguments list for functions (haven't found a clean way yet), so the
calltips for function tags are pretty useless.
There is still much to be done, but it's a good start.
Cheers,
Matthew Brush
Hi,
I've finally found some time to integrate my GProject plugin into
geany-plugins; for those who like git, the result is here:
https://gitorious.org/geany-plugins-gproject/geany-plugins-gproject
For those who dislike it, the patch is here:
http://db.tt/esDNpPw
I hope I've updated all the necessary files. The automake build should
be working correctly; however, in the waf build I'm not sure how to
integrate icon cache rebuild into the waf script. From what I could
see no other plugin ships with its own icons and even though Geany's
waf script contains the necessary code to rebuild the icon cache, I'm
not sure how to integrate it properly into the plugin build system.
Anyone willing to help?
Cheers,
Jiri
Hi Hans,
I just tried to check out the plugins repository on Windows (again
after a long time) and I notice a strange problem:
The SVN checkout breaks at checking out geanypg/src/aux.c because
Windows doesn't seem to allow files and directories containing "aux" in
their names[1]. This is weird but that's what Windows is.
Could you please rename "aux.c" to something else so Windows is happy
again?
Thank you.
[1] http://svn.haxx.se/tsvnusers/archive-2006-01/0090.shtml
Regards,
Enrico
--
Get my GPG key from http://www.uvena.de/pub.asc