Devel January 2010

devel@lists.geany.org

9 participants
15 discussions

Re: [Geany-devel] [Bug] When saving a modified file, a new empty line is added
by Maxime Pacary 18 Jan '10

18 Jan '10

Thanks for your answers. I totally agree that a popup dialog for that would be ugly and annoying. However, I think that this issue is quite important, since enabling that feature by default can be strongly distrurbing for PHP development. After some thinking, I would suggest that : - the feature "*new line at end of file*" would be a drop-down list instead of a checkbox, with options "*according to file type*" (default), "*always*", "*never*" - when option "*according to file type*" is selected : - when (for example) a C/C++ file is saved, a new empty line is automatically added if necessary - when a PHP (or Javascript, CSS, HTML, SQL, XML, YML...) file is saved, no new empty line is added - details about file types requiring a "final empty line" or not, would be available in the manual. This way, Geany's default behavior would be convenient for all programming languages (but user can "force" the behavior to whatever he prefers), and the user wouldn't be annoyed by any warning message. Maxime Enrico Tröger a écrit : > On Sat, 28 Nov 2009 11:01:52 +0100, Frank wrote: > > >> On Thu, 26 Nov 2009 19:02:10 +0100 >> Maxime Pacary <mpacary(a)winsoft.fr> wrote: >> >> >>> A nice colleague knowing better Geany told me that this could simply >>> be disabled in preferences > files ; so please ignore that bug >>> report, sorry. However, it could be nice to warn the user if he works >>> on PHP files while having the feature "new line at end of file" >>> enabled. >>> >> I don't see any big reason for adding a warning, maybe a pop-up or >> something like that. In time this will be more annoying as helpful from >> my point of view. I recommend just deactivate the feature and ensure to >> insert empty line manual in case its needed. >> > > Exactly. > If you don't want Geany to insert new blank lines at the end of files, > deactivate this feature. Adding a warning in whatever way, is just more > annoying than helpful. > > > And to be able to receive further answers and be able to send messages, > you first need to subscribe to this mailing list. Thanks. > > http://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel > > > Regards, > Enrico > >

4 5

Nightly build changes
by Enrico Tröger 17 Jan '10

17 Jan '10

Hi, I recently enabled the Spell Check, GeanyLua and Pretty Printer plugins in the plugin nightly builds for the GTK 2.8 compatibility test. They weren't built previously because of unmet dependencies (enchant, lua and libxml2) but I just installed those and so the mentioned plugins are not built as well. And GeanyVC is now built with GtkSpell support enabled. So in theory, we are able to catch even more possible errors :). Another change was that I wrote a small tool [1] which tries to load the plugins very similar as Geany would do (it's actually based on the code in Geany). Inspired by the recent discussion on the Geany mailing list where a user had problems loading the Spell Check plugin because of unresolved symbols in the plugin (which was due a bug in the code which was already fixed in the meantime), I thought about discovering such issues during the nightly builds. Since plugins are just shared libraries, we don't get normal linker errors as we would get for Geany itself. Instead, such errors occur first when trying to load the plugin into Geany when the linked symbols are actually resolved (or tried to resolve :D). So, I finally came to the clue that we could 'emulate' loading a plugin by dlopen() it, read some of the required symbols and just check whether it works. As said, the small tool tries to be as similar to what Geany does as possible. It's already included in the nightly build scripts, so we will get notices in case any plugin would fail. The good thing is, currently all built plugins pass the tests, yay. Both changes won't bring a real benefit for users but helps detecting problems in compatibility a bit earlier. As usual, the current status information about the nightly builds can be found on http://nightly.geany.org. And since today, the site is also availale via geany.nightlybuilds.org, thanks to Dominic Hopf :). [1] http://geany.svn.sf.net/viewvc/geany/trunk/scripts/plugin_test.c?revision=4… Regards, Enrico P.S.: sorry for the long and boring story but maybe someone finds it as interesting as me :). -- Get my GPG key from http://www.uvena.de/pub.asc

3 2

Moved some LaTeX specific code to geanyLaTeX
by Frank Lanitz 16 Jan '10

16 Jan '10

Hi fans and users of Geany ;) As not everybody is might not reading the SweetGeany's subversion announcements inside the IRC channel or the subversion commits mailing list I just want to inform you about a recent change I did for LaTeX support on Geany's current subversion version (r4524). With svn r4524 I moved some of the very LaTeX specific code out of the Geany core code into geanyLaTeX(1) plugin with svn r1126. At the moment its about the code, which is auto closing the \begin{] and \begingroup{} environments. If you are interested into this changes, please checkout a recent version of geanyLaTeX plugin via svn co https://geany-plugins.svn.sourceforge.net/svnroot/geany-plugins/trunk/geany… and compile it against a recent build of Geany. Please take care, as it will most probable compile with geany plugin API v169, but due its also depending on removing the function out of Geany itself, it might can have some funny effect if you didn't ensure to use a version below the above mentioned svn version. You have been warned ;) Please also check the documentation (as pdf inside svn inside doc/) for info how to configure it. Known issues: I'm happy nearly everything is working now from inside the plugin - at least from my current best knowledge. There is only one piece missing with setting the correct indent on the closing \end{} or \endgroup{}. So in such a case: \begin{table} \begin{tabular} the completion for the tabular environment will be without indent so it will look like: \end{tabular} \end{table} As this is from my point of just annoying, but a non blocker I committed the changes to subversion for some further peer testing. However this is getting fixed soon. Given this, I'd be happy for any feedback, either positive or negative. Happy TeX'ing Frank (1) http://frank.uvena.de/en/Geany/geanylatex/ -- Frank Lanitz <frank(a)frank.uvena.de>

1 0

Blanklines addons plugin
by Eugene Arshinov 12 Jan '10

12 Jan '10

Enrico, I'd like to remind you about my Blanklines "subplugin". When will it be committed to trunk? I attach the patch for geany-plugins r1118. Previous discussion: <http://lists.uvena.de/pipermail/geany-devel/2009-September/001311.html> Best regards, Eugene.

2 7

Re: [Geany-devel] Geany-devel Digest, Vol 21, Issue 14
by Lionel Fuentes 02 Jan '10

02 Jan '10

Dominic >> I like the website :) I have just one remark for the CodeNav plugin' "about" section : " Actually, it will make it possible to : - switch between header and implementation - go to a file by typing its name" -> you should add line breaks before the "-". And I definitely should implement this second part :p Lionel.

2 1

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

Devel January 2010