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,
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 guys,
During the last weeks a huge number mails at this list was stating to
make usage of GObject on building up a new plugin interface. It has been
talked about libpeas and adding support for Vala, Python etc. Before we
do discuss any further I'd like to point to an email Enrico sent
earlier this year onto this list:
http://lists.uvena.de/geany-devel/2011-February/003905.html
Originally Geany wasn't designed/coded to work with GObject. Moving to
an plugin interface using this would most likely cause rewriting of a
lot of code. However, if really somebody of you like to go this
further I suggest to start a new branch where all changes can be
tracked in.
But before we can discuss about the positive/negativ points I just
want to ask who likes to take over this task as a kind of lead
engineer and project manager to be the lead here having in mind it will
most likely not a 5-minute-task?
Cheers,
Frank
--
http://frank.uvena.de/en/
Dear devs,
Just pressing and holding a key pauses every ~10 characters. This is
only the case in a document when working on a pre-existing file, a new
document is as fast as can be.
What could be causing this? Does anybody else have the same problem?
I'm working on a php/Drupal project and use the geanyprj plugin to
index all files.
Harold
I removed all file paths from the dedug messages as it contains the
name of our client and the project...
11:06:33: Geany INFO : Geany 0.21 (svn >= r5584), en_US.UTF-8
11:06:33: Geany INFO : GTK 2.22.0, GLib 2.26.1, GIO
11:06:33: Geany INFO : System data dir: /usr/local/share/geany
11:06:33: Geany INFO : User config dir: /home/harold/.config/geany
11:06:34: Geany INFO : Added filetype Genie (52).
11:06:34: Geany INFO : Added filetype Scala (53).
11:06:34: Geany INFO : Loaded: /usr/local/lib/geany/addons.so (Addons)
11:06:34: Geany INFO : Loaded: /usr/local/lib/geany/filebrowser.so
(File Browser)
11:06:34: Geany INFO : Loaded: /usr/local/lib/geany/geanylipsum.so
(GeanyLipsum)
11:06:34: Geany INFO : Loaded: /usr/local/lib/geany/geanyprj.so (Project)
11:06:34: Geany INFO : Plugin "/usr/lib/geany/filebrowser.so" already loaded.
11:06:34: Geany INFO : Plugin "/usr/lib/geany/geanyprj.so" already loaded.
11:06:34: Geany INFO : <document path>.css : CSS (UTF-8)
11:06:34: Geany INFO : Bad color '0x0'
11:06:34: Geany INFO : Bad color '0x0'
11:06:54: Geany INFO : <document path>.php : PHP (UTF-8)
11:06:54: Geany INFO : Loaded /usr/local/share/geany/php.tags (PHP),
2338 tag(s).
11:06:54: Geany INFO : Bad color '0xfffffff'
11:06:54: Geany INFO : <document path>.php : PHP (UTF-8)
11:06:54: Geany INFO : <document path>.php : PHP (UTF-8)
11:06:55: Geany INFO : <document path>.php : PHP (UTF-8)
11:06:55: Geany INFO : <document path>.css : CSS (UTF-8)
11:06:56: Geany INFO : <document path>.php : PHP (UTF-8)
11:06:56: Geany INFO : <document path>.php : PHP (UTF-8)
11:06:57: Geany INFO : <document path>.module : PHP (UTF-8)
11:06:57: Geany INFO : <document path>.info : None (UTF-8)
11:07:03: Geany INFO : <document path>.css : CSS (UTF-8)
11:07:34: Geany INFO : <document path>.css : CSS (UTF-8)
11:08:05: Geany INFO : <document path>.php : PHP (UTF-8)
11:08:19: Geany INFO : <document path>.php : PHP (UTF-8)
11:08:30: Geany INFO : <document path>.php : PHP (UTF-8)
11:08:55: Geany INFO : unknown : None (UTF-8)
11:09:22: Geany INFO : <document path>.php : PHP (UTF-8)
11:12:15: Geany INFO : unknown : None (UTF-8)
11:12:26: Geany INFO : unknown : PHP (UTF-8)
11:12:57: Geany INFO : <document path>.php : PHP (UTF-8)
11:13:51: Geany INFO : <document path>.php : PHP (UTF-8)
11:14:56: Geany INFO : <document path>.php : PHP (UTF-8)
Hi list,
I received a patch, haven't got around to reviewing it yet.
Begin forwarded message:
Date: Sun, 13 Mar 2011 00:33:11 +0100
From: Nicolas Sierro <nicolas(a)sierro.net>
To: nick.treleaven(a)btinternet.com
Subject: Geany feature: follow project path
Dear Nick,
I started using Geany recently and found annoying that changing project
did not change the working directory in the VTE. I therefore attached a
likely trivial patch that implements this feature. It would probably
benefit from having a check box to toggle it in the project property
dialog, but I did not implement it.
I hope you can make use of my patch.
Best regards,
Nicolas
Regards,
Nick
Hi,
It's one month since I initially sent this, and the main developers
seem more or less online now, so I'm resending it.
--
On several occasions, we discussed that it would be a good thing to
save the find/replace settings. So I wrote it.
Note that when you check "regular expressions", Geany remembers the
"case sensitive" state, and restores it when regex is unchecked. This
remembered state is not saved, so after restart, you'll get "regular
expressions" and "case sensitive" as you see them.
This remembered state was partially wrong, shared between the Find and
Replace dialogs (their settings are separate), so I created separate
states. Truth to be said, I can't grasp why regex and case are bound
like that.
BTW, is there any reason to stash_group_display(fif_prefs) each time
the FiF dialog is shown, instead of doing it once on dialog creation?
The fif settings won't change between invokations.
--
E-gards: Jimmy
*NOT FOR REAL USE*
Just an example how Clang's code completion support may be added to
the geany. Code is awful, Makefile.in edited by hand, etc. Usage as is
not recommended. But prooves the concept and actualy works. I hope
someone will fix it so it became usable.