Devel February 2009

devel@lists.geany.org

7 participants
15 discussions

"Auto-close quotes and brackets" - addition request
by JGuillaume (ioguix) de Rorthais 05 Feb '09

05 Feb '09

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, Happy New Year to you guys ! Best wish to you and Geany :) In reply to this discussion on the geany list: http://lists.uvena.de/pipermail/geany/2008-December/003878.html I did my own version of the patch (in attachment). It still have following some flaws: - - when you insert an autoclosed char and immediatly delete it, the non-autoclose code kicks in anyway (I'm not sure how/where to deal with the delete keys) - - when inserting a quote (double or not), coming back before it and inserting another one, the non-autoclose code kicks in anyway. Should we test the next-char before non-autoclosing ? - - the test for matching bracket seems a bit too greedy as autoclose often doesn't kicks in because of a closing bracket few lines after. Hadn't notice any lag with this code, however I wasn't notice lag with Enrico's patch neither...so someone with an older computer should probably check that. Thanks for your next answer and review :) - -- Guillaume (ioguix) de Rorthais -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkllg9QACgkQxWGfaAgowiIFBgCfa4Wrn7gOUrwUarMMAbgxI+Yy hVwAn1FWzNd8eQeXL0oApICzvTdKGRF6 =WD/5 -----END PGP SIGNATURE-----

4 6

Cleanup in the VC menu
by Thomas Martitz 02 Feb '09

02 Feb '09

The attached patch moves the stuff in the tools->VC menu into Current File Current Directory Current Basedirectory This makes each menu cleaner. Additionally, it allows adding new functionality without messing up the current single menu even more, such as revert for directory and basedirectory, or commit of single files etc in the future. Code-wise it does a little cleanup. The creation of each submenu is in a seperate function, as well as the initialization of the hotkeys. -- Kind regards --------

5 19

Update to build support
by Lex Trotman 02 Feb '09

02 Feb '09

Hi All, Sorry for the long silence, I had a family health problem which had me away from home and with only access to email, no upload or download. Now that I am back I will be able to get on with the build-system updates, once I remember where I was up to ;-). Since I stuffed up copying the source to my laptop nothing has happened in the interim. As I remember we were trying to come to a conclusion about commands for header files for C and C++ which are currently explicitly prevented from performing any compile or build. The C++ work I have done in the meantime has re-inforced my desire to be able to at least compile C++ headers by themselves to get out the syntax typos because they tend to cause a lot of "flow on" errors in the .cpp file and C++ generates such enormous error messages (see http://www.parashift.com/c++-faq-lite/templates.html#faq-35.17 for an example). Also I have noticed that Geany 0.15 is very slow when there are lots of errors, maybe the regex parse is a bit slow, anyway that just makes it more important to compile the .hpp file first. The question seems to be how we handle having different commands for the header files (different to the .cpp files that is) without creating new filetypes for them. My last proposal was for a "variant" of the filetype which allowed different commands. The variant was identified by a subset of the filetypes extensions. This is a slightly general solution configurable in the filetypes or preferences files, or another option is something hard coded specifically for header files, not my favourite :(. Any other suggestions? Cheers Lex

4 16

Branching im geany-plugins SVN
by Frank Lanitz 02 Feb '09

02 Feb '09

Hi guys, As you might have seen, last week I created a branch for redesigning of GeanyVC's menu structure. For creating this, I branched the geanyvc subfolder from trunk. This was ok IMHO for this topic but made me thinking about how a branch could look like in future. I had a couple of ideas and like to start some kind of poll about this topic ;) 1.) Always branch complete trunk with all plugins so e.g. waf is still working. This would make some things more easier e.g. handling with git svn, but would force somebody who did a svn co on the branch to waste space on the hard drive 2.) Creating a folder structure similar to the tags section and then putting the branch into the right folder: |-- branches | |-- backupcopy | |-- filetree | |-- geany-mini-script | |-- geanydbg | |-- geanydebug | |-- geanydoc | |-- geanylatex | |-- geanyprj | |-- geanysendmail | |-- geanyvc | |-- instantsave | `-- spellcheck |-- tags | |-- backupcopy | |-- filetree | |-- geany-mini-script | |-- geanydbg | |-- geanydebug | |-- geanydoc | |-- geanylatex | |-- geanyprj | |-- geanysendmail | |-- geanyvc | |-- instantsave | `-- spellcheck `-- trunk 3.) Branching as needed analog to GeanyVC_menu_redesign, were only code is included, that is really needed for the branch. I'd prefer suggestion 1, but I really like to know your opinion. ;) Cheers, Frank -- http://frank.uvena.de/en/

4 4

ANN: String freeze for Geany 0.16
by Frank Lanitz 02 Feb '09

02 Feb '09

Hi translators and friends of Geany, I'm glad to announce our string freeze for Geany 0.16 which is planned for being released not far in future. I'd be very happy if you could send a patch or complete file with translation to either the geany-i18n mailing list or direct to me within the next week so we can include it to the next release (around February, 11). To make it more easy for you I've already uploaded updated versions of the po files to svn with r3537. You can access them from http://geany.svn.sourceforge.net/viewvc/geany/trunk/po/ or by checking out the svn tree of Geany by using e.g. svn co https://geany.svn.sourceforge.net/svnroot/geany/trunk geany Fans of git can also use the interface provided by http://git.geany.org by using git clone http://git.geany.org/git/geany Also on http://www.geany.org/i18n/ are statistics and daily updated files available. Because of I had a couple of requests in past, together with Alex we uploaded translation files to launchpad for testing purpose. Since testing is still in progress without any final decision, I'd like to ask you to using sending patches and/or complete po files direct to me or to list. We are trying to have all translations complete by 2009-02-11. If your language was translated by two or more in past, please double check directly with them or by pinging me, so we don't need to translate same things two or three times. Also please feel to ping me for every question or if you like to start a new translation for an unsupported language. Thanks and happy translating ;) Frank -- http://frank.uvena.de/en/

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

Devel February 2009