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
Dear Geany devs,
Some time ago I received the attached patch though this list (from
Enrico?). I really love the added functionality to prevent duplicate
automatically added quotes and brackets.
Can this be added to Geany itself? Ideally this would be activated
with a checkbox in prefs > editor > completions.
-tnx!-
Harold
Hi,
We're planning to make a 0.19.2 release very soon with just one
important fix - the failure to always report a save error to the user
whenever POSIX saving fails.
Any other fixes will be delayed to the 0.20 release which hopefully
will be in a few weeks time. (We haven't agreed the string freeze just
yet but it will be soon).
Nick
Hi,
Do we plan to update scintilla anytime soon? If not, would it be
possible to apply a small (7 lines) change from scintilla r3465, which
speeds up the rectangular selection about 20 times? It's perfectly
compatible with our revision.
--
E-gards: Jimmy
Hi!
I'm Michael from Vienna and am using Geany for several month (used SciTE
before).
Geany has a lot of features I like. One of the rare nuisances is the
"Find"-dialog-box that rejects to set "Case sensitive" by default. There is an
option in the Geany configuration file for this but it is ignored by Geany.
Today I took a look into the source code and found the reason why. The default
is loaded, but when the checkbox is created there is line of code missing to
actually *use* the default settings.
I'm using version 0.19 of Geany on Gentoo-Linux. Here is my patch:
--- src.orig/search.c 2010-05-11 12:10:31.000000000 +0000
+++ src/search.c 2010-11-27 14:36:06.189515685 +0000
@@ -273,6 +273,7 @@
g_object_set_data_full(G_OBJECT(dialog), "check_case",
g_object_ref(checkbox1),
(GDestroyNotify)g_object_unref);
gtk_button_set_focus_on_click(GTK_BUTTON(checkbox1), FALSE);
+ gtk_toggle_button_set_active(GTK_TOGGLE_BUTTON(checkbox1),
settings.fif_case_sensitive);
checkbox2 = gtk_check_button_new_with_mnemonic(_("Match only a _whole
word")); g_object_set_data_full(G_OBJECT(dialog), "check_word",
Greetings, Michael
Hi,
I started reading the introduction page on plugin development:
http://www.geany.org/manual/reference/howto.html
I copy pasted the program and fired a shell to compile it , this is what I
got:
shankhs@shankhs:~/geany/shankhs$ gcc -c plugin.c -fPIC `pkg-config --cflags
geany`
shankhs@shankhs:~/geany/shankhs$ gcc plugin.o -o plugin.so-shared
`pkg-config --libs geany`
/usr/lib/gcc/i686-linux-gnu/4.4.5/../../../../lib/crt1.o: In function
`_start':
(.text+0x18): undefined reference to `main'
collect2: ld returned 1 exit status
The last error was a show stopper , I wasn't able to go forward :( .
I am not great with pkg-config, so can anybody please help me in finding a
solution to this problem?
Where is geany's lib folder exactly installed? and where should I put my
plugin to let geany know?
Thank you
shankhs
Hi,
I just tried running ./autogen.sh and got this:
checking for GIO... configure: error: Package requirements (gio-2.0)
were not met:
No package 'gio-2.0' found
...
make[1]: *** [config.status] Error 1
I think this may be due to build/treebrowser.m4 not disabling itself if
GIO is not found.
Nick
To see this in action, create a Java file (the default one will do) and
add the following functions:
public int[] myTestFunctionOne(){
return null;
}
public String[] myTestFunctionTwo(){
return null;
}
Save the file and check the generated tags. The second function will be
correctly found, but another tag "String" will be generated, pointing
to the same line. Autocompletion of the function name works fine, as
does the parameter listing when the name is complete and you type "(".
If I get a chance over the weekend I'll take a look at the lexer.
Remind me (and I really should remember this), is it based on ctags?
ie. If I make a working patch, should I submit it to the ctags project?
Jon