Devel August 2010

devel@lists.geany.org

20 participants
35 discussions

[PATCH] FIx document_need_save_as() logic
by Erik de Castro Lopo 09 Sep '10

09 Sep '10

Hi all, Had a minor niggle which i decided to fix. If I do: geany some_file_which_doesn't_exist geany will open a new tab with the right file name for the tab. If I then add some code/text and try to save the file, geany currently throws up a SaveAs dialog box even though it was already given a filename earlier. The attached patch fixes this (tested on Linux) by changing the needs_save_as logic to ignore doc->real_path and only check doc->file_name. Cheers, Erik -- ---------------------------------------------------------------------- Erik de Castro Lopo http://www.mega-nerd.com/

3 6

STATA support
by Alessio Caiazza 09 Sep '10

09 Sep '10

Hi, some STATA programmers asked me to develop a STATA lexer for geany here at work. I did it in the past month and they tested it. Today a opened a feature request [1] on SourceForge but I discovered that Scintilla gets a major update (rel 2.20). :( Now I'm working on porting my patches to scintilla 2.20, but if geany team didn't plan to update Scintilla soon they can review my lexer. bye, Alessio [1] https://sourceforge.net/tracker/?func=detail&aid=3041939&group_id=153444&at… -- Alessio Caiazza Agenzia Regionale di Sanità Toscana Viale Giovanni Milton 7, 50129 Firenze alessio.caiazza(a)ars.toscana.it | Fax. 055.3841405

2 1

Russian version of Geany 0.19 manual online
by Frank Lanitz 28 Aug '10

28 Aug '10

Hi users and friends of Geany, A couple of weeks Denis Koryavov sent a Russian translation for Manual of Geany 0.19. For some reason I missed to forward it to the list (mea culpa) but today I've finally uploaded his version to the Geany server so everybody can access it by going to http://geany.org/manual/0.19_ru/ Thanks very much. Its an impressive work! Thanks, Frank -- http://frank.uvena.de/en/

1 0

Geany-Plugins: Having just one copy of GPL inside source tree
by Frank Lanitz 25 Aug '10

25 Aug '10

Hi, during the work on Updatecheker I recognized another time that nearly every plugin is having its own copy of GPL. As most of the plugins code is licensed under GPL2+, what do you think of moving the individual copies of GPL into a central, geany-plugins-License as the package is most likely distributed under a common license and this would save a lot of space inside tarball etc.? Cheers, Frank -- http://frank.uvena.de/en/

3 5

build geany plugins on Windows
by Johann SAUNIER 24 Aug '10

24 Aug '10

Hello world, I need to apply my own patches to Geany and Geany-plugins too, but I now work on Windows. I can build Geany using makefile.win32 but I can't find an equivalent for Geany-plugins. I know Geany-plugins is built on Windows by maintainers because it's available as a setup.exe but I can't find the way to do it myself. Any idea ? Thanks

4 5

[PATCH] Minor autotool cleanups
by Erik de Castro Lopo 24 Aug '10

24 Aug '10

Hi all, Patch below fixes a number of warnings when running autogen.sh. Cheers, Erik -----------8<-----------8<-----------8<-----------8<-----------8<----------- --- Makefile.am 2010-06-16 15:22:19 +0000 +++ Makefile.am 2010-08-03 22:25:32 +0000 @@ -4,6 +4,8 @@ AUTOMAKE_OPTIONS = 1.7 +ACLOCAL_AMFLAGS = -I m4 + WIN32_BUILD_FILES = \ geany_private.rc \ win32-config.h \ --- configure.ac 2010-06-12 13:42:50 +0000 +++ configure.ac 2010-08-03 22:25:32 +0000 @@ -3,6 +3,7 @@ AC_INIT(configure.ac) AM_INIT_AUTOMAKE(geany, 0.20) +AC_CONFIG_MACRO_DIR([m4]) m4_ifdef([AM_SILENT_RULES],[AM_SILENT_RULES([yes])]) @@ -22,7 +23,6 @@ AC_MSG_ERROR([No C++ compiler found. Please install a C++ compiler.]) fi -#AC_PROG_RANLIB AC_PROG_INSTALL AC_PROG_LN_S AC_PROG_INTLTOOL -----------8<-----------8<-----------8<-----------8<-----------8<----------- -- ---------------------------------------------------------------------- Erik de Castro Lopo http://www.mega-nerd.com/

2 4

New Plugin: Updatecheker
by Frank Lanitz 23 Aug '10

23 Aug '10

Hi, I've committed today a new plugin to the geany-plugins project. As the name might already imply, its a plugin to check whether there is a new Geany version available or not. For compiling you will need to use the waf build system (integration with autotools not finished now) and the devel package of libsoup. The general function is not very 'exciting', but would be happy for any feedback. Cheers, Frank -- http://frank.uvena.de/en/

1 0

[PATCH] Behavior of opening filenames with colons from the command line
by Colomban Wendling 19 Aug '10

19 Aug '10

Hi, I saw yesterday a discussion about opening files that ends with something like ":2" [1], and even if it's already fixed, I don't feel that the behavior is neither the best nor the more intuitive. The current behavior is to: 1) if the file exists, don't try to extract the line/column information from the name 2) otherwise, extract these information without further checks. That's fine in most cases (who has files that ends with :<number> anyway? [2]) but what if I have a file named "file:1" and I want to open it at line 43? I'd think I just have to type "file:1:43", as I'd have done with any other file. But no, of course, it tries to open "file" at line 1, column 43. Then it's (IMO) quite like you can't open files that ends with :<number> on CLI unless you specify both line and column information (like before the bug was fixed), because the behavior is not the same than with other filenames. I then would think it's better to do: 1) if the file exists, don't extract line/columns information 2) otherwise, try to strip line information 3) if the file exists, stop here 4) otherwise, try to strip column information from the end [3] 5) if the file exists, stop here 6) otherwise, restore the name that was given, without stripping line and column. This seems to me to be a better behavior, since it prefers opening an existing file than a non-existing one; and if the file doesn't exist, prefer to keep the full name given. The joined patches implements this (see below). But OTHO, it makes harder to open "file:0" at line 1 if both "file:0" and "file:0:1" exists: it needs to hack in some way, for example typing "file:0:01" rather than "file:0:1"... Then we may want to complicate the thing a little more and prefer the file that exists with the shorter filename (then given "file:0:1" we would prefer "file" at line 0, column 1 over "file:0" at line 0 over "file:0:1" if all three exists...). If so, I'd be happy to implement it :p Any thoughts? About the two patches: * 0001-cli-line-column-prefer-existing-files-2.patch is my original implementation, but as I rewritten it from scratch, it is very different from the original and almost all the code changes, so maybe you don't like it (thought it seems to be 37% faster [4]). * 0001-cli-line-column-prefer-existing-files.patch does the same but only changes a little the current code. It is less "beautiful" IMHO because the design doesn't fit very well what I wanted to do, but the large majority of the code is the same. Best regards, Colomban [1] Debain's bug #551358 (http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=551358), even though I think it should be closed... [2] and because of this, perhaps all this email is useless and time-wasting... [3] yes, line/column has to be swapped here, but that's a detail that needlessly complicates the explanation. [4] tested with the modifications, with 3000000 passes over 6 different inputs (34.375s vs 21.677s). Yes, it probably doesn't matter, and yes I like benchmarking useless things.

2 9

ANN: New Release: Geany 0.19.1
by Nick Treleaven 19 Aug '10

19 Aug '10

Hi all, Geany 0.19.1 has been released. This is a bugfix release including fixes for broken autocompletion, document detection on Windows and various other issues. There are also some tweaks including ignoring background colors when printing. For a list of changes in Geany 0.19.1, please see: http://www.geany.org/Documentation/ReleaseNotes All downloads can be found on http://download.geany.org. We want to thank the many contributors who helped spotting, reporting and fixing bugs. Thank you! Regards, Nick

1 0

[PATCH] Fix bug 3037795 (miltiline comment closing indentation)
by Dejan Cabrilo 19 Aug '10

19 Aug '10

Hello all, I'm new here and I hope this is the right way to submit this patch. Anyway, the bug was this: http://sourceforge.net/tracker/?func=detail&aid=3037795&group_id=153444&ati… This manifested in PHP like this: /** * Miltiline comment */ _auto indentation has an extra space. The reason for this was that auto_multiline function in editor.c trapped code to fix indentation after multiline comment in if (sci_get_style_at(sci, indent_pos) == style). I'm not sure why this was added in the latest release (the check didn't exist earlier), so I just moved the code for fixing the indent before this condition. The patch is trivial and attached (it's against latest SVN). Thanks, Dejan

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

Devel August 2010