Re: [Geany-devel] Third party plugin publish and third party library bundle problem
On Sat, 2012-07-14 at 20:12 +0200, Dominic Hopf wrote: > It would be no big deal to introduce it again if you like. You can > just open another pull request for the plugins.geany.org website and > I'll have a look on it as soon as I find the time to do that. :) If you're going to add your plugin to the Geany-Plugins project as well, be advised I have another mail from Matthew flagged as "TODO" for the plugins.geany.org website. At present it is generating the navigation from a tagged release in Git. I like Matthews idea to add plugins from the master branch when they don't exist in the tagged release yet and add a hint to the generated page that that specific plugin is under development. Only thing missing is the implementation... :) Regards, Dominic -- Dominic Hopf http://dominichopf.de/ Key Fingerprint: A7DF C4FC 07AE 4DDC 5CA0 BD93 AAB0 6019 CA7D 868D signature.asc Description: This is a digitally signed message part ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] Third party plugin publish and third party library bundle problem
On Sat, 2012-07-07 at 13:39 +0800, Hong Xu wrote: > First, http://plugins.geany.org is a place for plugin list. But are > the third party plugins allowed here? All the pages seem working for > the plugins here: <https://github.com/geany/geany-plugins> including > the download page, installation page. We already had another section for "Thirdparty plugins" in the navigation. I removed the section because every of those three plugins mentioned there were outdated or moved into the Geany-Plugins project itself and that section thus wasn't necessary anymore. :) It would be no big deal to introduce it again if you like. You can just open another pull request for the plugins.geany.org website and I'll have a look on it as soon as I find the time to do that. :) Regards, Dominic -- Dominic Hopf http://dominichopf.de/ Key Fingerprint: A7DF C4FC 07AE 4DDC 5CA0 BD93 AAB0 6019 CA7D 868D signature.asc Description: This is a digitally signed message part ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] IRC Channel Topic
On Fri, 2012-06-22 at 20:51 +1000, Lex Trotman wrote: > The IRC channel topic still says 0.21 is out! While still true its a > bit behind :) Updated. Thanks for the hint. :) Best Regards, Dominic -- Dominic Hopf http://dominichopf.de/ Key Fingerprint: A7DF C4FC 07AE 4DDC 5CA0 BD93 AAB0 6019 CA7D 868D signature.asc Description: This is a digitally signed message part ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] Geany Plugins Build using Waf fails from current Git master
On Wed, 2012-05-09 at 21:22 +0200, Quentin Glidic wrote: > On 09/05/2012 20:28, Dominic Hopf wrote: > > Hey guys, > > > > building Geany Plugins from Git fails currently fails here. The output: > > > > http://pastebin.geany.org/kota1/ > > > > This doesn't actually mean this is an issue with Geany-Plugins, I'm > > running the current Fedora 17 Beta state here with updates-testing > > enabled. ;) > > > > I was hoping someone of you could point me in the right direction where > > to search for the cause anyway. :) > > > > Best Regards, > > Dominic > > > It’s a Vala related error, a name collision. I submitted a patch for > this issue, see http://lists.uvena.de/geany-devel/2012-April/006759.html Builds fine here with the applied patch. Thank you guys! Best Regards, Dominic -- Dominic Hopf http://dominichopf.de/ Key Fingerprint: A7DF C4FC 07AE 4DDC 5CA0 BD93 AAB0 6019 CA7D 868D signature.asc Description: This is a digitally signed message part ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
[Geany-devel] Geany Plugins Build using Waf fails from current Git master
Hey guys, building Geany Plugins from Git fails currently fails here. The output: http://pastebin.geany.org/kota1/ This doesn't actually mean this is an issue with Geany-Plugins, I'm running the current Fedora 17 Beta state here with updates-testing enabled. ;) I was hoping someone of you could point me in the right direction where to search for the cause anyway. :) Best Regards, Dominic -- Dominic Hopf http://dominichopf.de/ Key Fingerprint: A7DF C4FC 07AE 4DDC 5CA0 BD93 AAB0 6019 CA7D 868D signature.asc Description: This is a digitally signed message part ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] Where have the thirdparty plugins gone?
On Sat, 2012-03-03 at 15:55 +0100, Dominic Hopf wrote: > On Fri, 2012-03-02 at 08:33 +0100, Frank Lanitz wrote: > > BTW: (I think) All other plugins inside the svn > > has been officially deprecated or moved into geany-plugins combined > > plugins project. > > Sounds like it is save to just remove them from the navigation at > http://plugins.geany.org/ then? Well, removed for now. Let me know in case I removed too much, I'll `git revert` it then ;) Best Regards, Dominic -- Dominic Hopf http://dominichopf.de/ Key Fingerprint: A7DF C4FC 07AE 4DDC 5CA0 BD93 AAB0 6019 CA7D 868D signature.asc Description: This is a digitally signed message part ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] Where have the thirdparty plugins gone?
On Mon, 2012-03-05 at 23:58 +0400, Eugene Arshinov wrote: > That was me who agreed to maintain the Mini-Script plugin. That > plugin is now inside geany-plugins. Also it seems to have a working > README. What should be done to place this README on the site? Hi Eugene, sorry for my late reply. There is nothing to do for you, there is a Cron job running the gencontent.sh [1] every night at 04:05 UTC. The thing with this currently is, that the new geanyminiscript plugin isn't in a tagged release, yet. I've lately changed the behavior of the gencontent.sh to generate the site only from a tagged release, because people were claiming about the consistency with the website and released versions of Geany-Plugins in several threads here on the list. I hope you are fine with waiting for the next Geany-Plugins release until it appears on the website? - Otherwise I will have to give the gencontent.sh script some more love. :) Best Regards, Dominic [1] https://github.com/geany/plugins.geany.org/blob/master/gencontent.sh -- Dominic Hopf http://dominichopf.de/ Key Fingerprint: A7DF C4FC 07AE 4DDC 5CA0 BD93 AAB0 6019 CA7D 868D signature.asc Description: This is a digitally signed message part ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] Where have the thirdparty plugins gone?
On Fri, 2012-03-02 at 08:33 +0100, Frank Lanitz wrote: > BTW: (I think) All other plugins inside the svn > has been officially deprecated or moved into geany-plugins combined > plugins project. Sounds like it is save to just remove them from the navigation at http://plugins.geany.org/ then? Regards, Dominic -- Dominic Hopf http://dominichopf.de/ Key Fingerprint: A7DF C4FC 07AE 4DDC 5CA0 BD93 AAB0 6019 CA7D 868D signature.asc Description: This is a digitally signed message part ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
[Geany-devel] Where have the thirdparty plugins gone?
Hi everyone, Lex pointed me to the issue, that the pages for the third-party plugins at http://plugins.geany.org/ are empty. I have to admit, that I maybe am not that up-to-date and thus, am not sure what actually happened to those plugins. Last thing I know of them is, that they were in the same SVN repository at SourceForge as Geany-Plugins. After the migration to GitHub they are gone - I guess that is intended. Does anyone know what happened to them? Do they exist anymore and just in another place? Or should I really remove them from the website? Regards, Dominic -- Dominic Hopf http://dominichopf.de/ Key Fingerprint: A7DF C4FC 07AE 4DDC 5CA0 BD93 AAB0 6019 CA7D 868D signature.asc Description: This is a digitally signed message part ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] Geany-Plugins: MAINTAINERS file
On Fri, 2012-01-06 at 19:52 +0200, Dimitar Zhekov wrote: > On Fri, 06 Jan 2012 10:29:30 +0100 > Frank Lanitz wrote: > > > We have just added a MAINTAINERS into git to add a single point to find > > who is responsible for a plugin. Please be so kind and sending in > > patches or updating the file on your own [...] > > Here's a patch. Applied, thanks. :) -- Dominic Hopf http://dominichopf.de/ Key Fingerprint: A7DF C4FC 07AE 4DDC 5CA0 BD93 AAB0 6019 CA7D 868D signature.asc Description: This is a digitally signed message part ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] Geany-Plugins: Adding a maintainer file
On Fri, 2011-12-30 at 11:54 +0100, Frank Lanitz wrote: > Well, I'd like to extend the point and suggest based on linux kernel > maintainer file: > An entry shall include the plugin name and > > Descriptions of section entries: > P: Person > M: Mail patches to: FullName > W: Web-page with status/info > S: Status, one of the following: >Supported: Someone is actually paid to look after this. >Maintained: Someone actually looks after it. >Odd Fixes: It has a maintainer but they don't have time to do > much other than throw the odd patch in. See below.. >Orphan: No current maintainer [but maybe you could take the > role as you write your new code]. >Obsolete:Old code. Something tagged obsolete generally means > it has been replaced by a better system and you > should be using that. > > Comments? I like this idea. Regards, Dominic -- Dominic Hopf http://dominichopf.de/ Key Fingerprint: A7DF C4FC 07AE 4DDC 5CA0 BD93 AAB0 6019 CA7D 868D signature.asc Description: This is a digitally signed message part ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] plugins.geany.org update - contents now generated from the latest Geany-Plugins release
Am Sonntag, den 18.12.2011, 19:17 +0400 schrieb Alexander Petukhov: > Hi Dominic, > > I didn't get clear how to deal with the newly created branch after a > bug is fixed in it: push branch to github, merge with master and push > master or whatever? Can you pls give some more details. If you are going to fix a bug which is present since 0.21.1, you would create the branch 0.21.1 from the tag, fix your stuff there, and push the branch upstream via `git push -u origin 0.21.1`. Then you of course also apply the fix to master, separately from the fix for the special version 0.21.1 using the git cherry-pick command: git checkout master git cherry-pick Regards, Dominic -- Dominic Hopf http://dominichopf.de/ Key Fingerprint: A7DF C4FC 07AE 4DDC 5CA0 BD93 AAB0 6019 CA7D 868D signature.asc Description: This is a digitally signed message part ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] plugins.geany.org update - contents now generated from the latest Geany-Plugins release
Am Samstag, den 17.12.2011, 17:05 +0100 schrieb Dominic Hopf: > [1] https://github.com/dmaphy/plugins.geany.org/commits/master The repository has moved to the Geany organisation. New link: https://github.com/geany/plugins.geany.org/commits/master Regards, Dominic -- Dominic Hopf http://dominichopf.de/ Key Fingerprint: A7DF C4FC 07AE 4DDC 5CA0 BD93 AAB0 6019 CA7D 868D signature.asc Description: This is a digitally signed message part ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
[Geany-devel] plugins.geany.org update - contents now generated from the latest Geany-Plugins release
Hi together, with today's commits [1] the behavior of the gencontent.sh has changed. The script now tries getting the README files from the latest Geany-Plugins release and not from git master anymore. For you as a plugin maintainer, this now means that you'd need to create a branch exactly named as the tag of the latest release and put changes to README files there as well in case they apply for an already released version of Geany-Plugins. gencontent.sh would look for changes in that branch then and not in master. In other words: plugins.geany.org now has the content of the README files of the tag 0.21.1. If you like to improve something there, the changes must be made to a branch called 0.21.1 created from the tag. This should apply to a common work flow when fixing issues in an already released version, so I guess no big deal for anyone of you. Feel free to correct me, if you think I am wrong with this. :) Any further suggestions or improvements are welcome, feel free to fork the stuff and open pull requests. ;) Best Regards, Dominic [1] https://github.com/dmaphy/plugins.geany.org/commits/master -- Dominic Hopf http://dominichopf.de/ Key Fingerprint: A7DF C4FC 07AE 4DDC 5CA0 BD93 AAB0 6019 CA7D 868D signature.asc Description: This is a digitally signed message part ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] Geany-Plugins: Adding a maintainer file
Am Samstag, den 17.12.2011, 16:12 +0100 schrieb Frank Lanitz: > Hi folks, > > What do you think of adding a maintainer file, which basically include > only three information: > > plugin-name, maintainer name, contact email. +1 -- Dominic Hopf http://dominichopf.de/ Key Fingerprint: A7DF C4FC 07AE 4DDC 5CA0 BD93 AAB0 6019 CA7D 868D signature.asc Description: This is a digitally signed message part ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] geany-plugins converted to git
Am Samstag, den 10.12.2011, 20:19 +0100 schrieb Frank Lanitz: > OK. I've just pushed to https://github.com/geany/geany-plugins > Have fun ;) I've updated http://plugins.geany.org/, replaced stuff pointing to the SourceForge SVN to now point to the GitHub page, added a ForkMe Banner and the GitHub logo at the bottom. Also, the gencontent.sh which generates sites from README files is now pulling the changes from the GitHub repository. For a full ChangeLog what I did, see https://github.com/dmaphy/plugins.geany.org Let me know in case you notice any issue our incorrectness, I'll fix it then. Best Regards, Dominic -- Dominic Hopf http://dominichopf.de/ Key Fingerprint: A7DF C4FC 07AE 4DDC 5CA0 BD93 AAB0 6019 CA7D 868D signature.asc Description: This is a digitally signed message part ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] Development website
Am Dienstag, den 08.11.2011, 01:22 +0100 schrieb Colomban Wendling: > Le 08/11/2011 00:21, Lex Trotman a écrit : > > On Tue, Nov 8, 2011 at 6:03 AM, Dominic Hopf wrote: > >> Hi Lex, > >> > >> Am Montag, den 07.11.2011, 08:09 +1100 schrieb Lex Trotman: > >>> Hi Website dudes, > >>> > >>> Just noticed that the Geany developers page still points to svn for > >>> latest hacking, so it isn't :) > >> > >> > >> Either someone already fixed it, or I'm blind. I can not find the page > >> you're claiming about. :s > >> > > > > Hi Dominic, > > > > http://www.geany.org/Contribute/Developers reached from front > > page->sidebar->contribute->developers Very good catch. I remember I originally wrote that page. :) While talking about that, I rewrote the "Dive Deeper" stub "Request SVN access for Geany-Plugins" at the very bottom of the page. It now is named "Fork us on GitHub". :) (Well, maybe a bit to early for Geany-Plugins, though) Hope you're fine with that stub. Regards, Dominic BTW: What about the issue trackers, do you intend them to rest at SourceForge? -- Dominic Hopf http://dominichopf.de/ Key Fingerprint: A7DF C4FC 07AE 4DDC 5CA0 BD93 AAB0 6019 CA7D 868D signature.asc Description: This is a digitally signed message part ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] [RFC] Document Messages
Am Montag, den 07.11.2011, 23:28 +0100 schrieb Enrico Tröger: > In what way this is better than the search field in the toolbar? Another point which wasn't mentioned in previous replies: It just shows up if you request it via keybinding. Otherwise it won't be displayed (if I understood Matthew correctly) and saves space on the screen. :) Regards, Dominic -- Dominic Hopf http://dominichopf.de/ Key Fingerprint: A7DF C4FC 07AE 4DDC 5CA0 BD93 AAB0 6019 CA7D 868D signature.asc Description: This is a digitally signed message part ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] Development website
Hi Lex, Am Montag, den 07.11.2011, 08:09 +1100 schrieb Lex Trotman: > Hi Website dudes, > > Just noticed that the Geany developers page still points to svn for > latest hacking, so it isn't :) Either someone already fixed it, or I'm blind. I can not find the page you're claiming about. :s Regards, Dominic -- Dominic Hopf http://dominichopf.de/ Key Fingerprint: A7DF C4FC 07AE 4DDC 5CA0 BD93 AAB0 6019 CA7D 868D signature.asc Description: This is a digitally signed message part ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] Geany-Plugins 0.21.1 released
Am Montag, den 31.10.2011, 12:09 +0100 schrieb Frank Lanitz: > Hi all, > > Due a little issue with source tarball of 0.21-release of Geany-Plugins > 0.21.1 has been released which fixes an issue of non working waf-build > system from inside the source tarball. This implies that distro packages using autotools to build to not need to update, do they? Regards, Dominic -- Dominic Hopf http://dominichopf.de/ Key Fingerprint: A7DF C4FC 07AE 4DDC 5CA0 BD93 AAB0 6019 CA7D 868D signature.asc Description: This is a digitally signed message part ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] Future of GeanyGDB - [was: Geany Plugins Warnings (again)]
Am Freitag, den 28.10.2011, 16:46 -0700 schrieb Matthew Brush: > > 1) > > > > There are guys out there who write C code and may use debugging plugins > > from within Geany. There are at least two alternative plugins which > > would do the job. I'd love to know your honest opinion which one you > > actually prefer. > > > > I think there's only the Debugger plugin as an alternative, no? I think I remember some other stuff as well, but this was quite long ago and I couldn't find those ad-hoc. The Debugger plugin looks quite better than GeanyGDB at a first quick view (I didn't had a chance to look deeper into it before). > > 2) > > > > Wasn't it discussed before that we maybe remove GeanyGDB after the 0.21 > > release? - I'm not sure about this and to lazy to investigate for the > > mails. :) > > I'd say if the Debugger plugin is in good enough shape, it would be ok > to remove GeanyGDB. I guess we should see how many people use it though > and ask them if they'd like to maintain it (ex. on the general geany list). Let's start a poll somewhere.. :) Regards, Dominic -- Dominic Hopf http://dominichopf.de/ Key Fingerprint: A7DF C4FC 07AE 4DDC 5CA0 BD93 AAB0 6019 CA7D 868D signature.asc Description: This is a digitally signed message part ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] [RFC] Geany Plugin Names
Am Samstag, den 29.10.2011, 19:19 +0200 schrieb Colomban Wendling: > Le 29/10/2011 14:25, Alexander Petukhov a écrit : > > 29.10.2011 14:22, Lex Trotman пишет: > >> you are right that any plugin packaged *separately* should indeed > >> have "geany" in the package name but that doesn't affect directory > >> names or plugin manager names > >> > > +1 > > > > package names are packaging teams buisness, > > as they are already named with "geany-" prefix (at least *.deb ones) > > no changes for them except new folder names. > > Yeah actually under Debian the plugin packages already have the "geany" > prefix removed, but all starts with "geany-plugin-": > > geany-plugin-addons > geany-plugin-codenav > geany-plugin-doc > geany-plugin-extrasel > geany-plugin-gdb > geany-plugin-gendoc > geany-plugin-insertnum > geany-plugin-latex > geany-plugin-lipsum > geany-plugin-lua > geany-plugin-prettyprinter > geany-plugin-prj > geany-plugin-sendmail > geany-plugin-shiftcolumn > geany-plugin-spellcheck > geany-plugin-treebrowser > geany-plugin-updatechecker > geany-plugin-vc > geany-plugin-webhelper On Fedora it's currently geany-plugins-$pluginname, which partly looks quite ugly: geany-plugins-addons geany-plugins-common geany-plugins-geanydoc geany-plugins-geanygdb geany-plugins-geanylatex geany-plugins-geanylua geany-plugins-geanyprj geany-plugins-geanysendmail geany-plugins-geanyvc geany-plugins-pretty-print geany-plugins-spellcheck geany-plugins-updatechecker geany-plugins-webhelper geany-plugins-codenav geany-plugins-geanyextrasel geany-plugins-geanygendoc geany-plugins-geanyinsertnum geany-plugins-geanylipsum geany-plugins-shiftcolumn geany-plugins-treebrowser Regards, Dominic -- Dominic Hopf http://dominichopf.de/ Key Fingerprint: A7DF C4FC 07AE 4DDC 5CA0 BD93 AAB0 6019 CA7D 868D signature.asc Description: This is a digitally signed message part ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] [RFC] Geany Plugin Names
Am Freitag, den 28.10.2011, 22:41 -0700 schrieb Matthew Brush: > Anyway, just a thought to make things more consistent and less > redundant. It seems like while converting and moving to Git would be > an > ideal time to do this. Feel free to +1, -1, comment or ignore. > +1 :) -- Dominic Hopf http://dominichopf.de/ Key Fingerprint: A7DF C4FC 07AE 4DDC 5CA0 BD93 AAB0 6019 CA7D 868D signature.asc Description: This is a digitally signed message part ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] Future of GeanyGDB - [was: Geany Plugins Warnings (again)]
Am Freitag, den 28.10.2011, 16:02 -0700 schrieb Matthew Brush: > The only plugin with non-trivial (by way of quantity) warnings to fix > was GeanyGDB. I don't know if this is maintained any more or if it's > needed with having the Debugger plugin, but if it is, the author(s) > should go through and fix all their `const` usage themselves. The > attached patch for GeanyGDB only fixes a few usages but exposes much > more warnings, so it might be of little use. The original author of this plugin was Jeff Pohlmeyer, I'm afraid he will not read this, though. I took over the "maintainership" long time ago, approx. at the beginning of 2010 (or maybe earlier) to not have an unmaintained plugin within the Geany-Plugins project. Seems I was out of my estimation regarding what it means to maintain such an amount of C code written by someone else - having in mind that I'm not that skilled in C (I'd call myself rather a beginner in writing C). I actually didn't wrote C since a few month now and also do not use GeanyGDB at present. I appreciate any efforts and patches which may improve GeanyGDB and would apply any contributed stuff for that plugin, but I'd like to discuss some questions (IIRC some may also were earlier discussed before): 1) There are guys out there who write C code and may use debugging plugins from within Geany. There are at least two alternative plugins which would do the job. I'd love to know your honest opinion which one you actually prefer. 2) Wasn't it discussed before that we maybe remove GeanyGDB after the 0.21 release? - I'm not sure about this and to lazy to investigate for the mails. :) 3) Is there anyone out there who alternatively would like to maintain and improve GeanyGDB (and is more skilled in C than me :) ). 4) I of course appreciate Matthews patch and like to apply it, but that most likely should wait at least until we moved to GitHub with Geany-Plugins, should it? Regards, Dominic -- Dominic Hopf http://dominichopf.de/ Key Fingerprint: A7DF C4FC 07AE 4DDC 5CA0 BD93 AAB0 6019 CA7D 868D signature.asc Description: This is a digitally signed message part ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] GIT commit mails format
Am Montag, den 24.10.2011, 23:45 +0200 schrieb Enrico Tröger: > >Nothing but a big "+1" ;) +1 -- Dominic Hopf http://dominichopf.de/ Key Fingerprint: A7DF C4FC 07AE 4DDC 5CA0 BD93 AAB0 6019 CA7D 868D signature.asc Description: This is a digitally signed message part ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] Plugins README / web pages
Am Montag, den 10.10.2011, 22:58 +0200 schrieb Enrico Tröger: > > However, Dominic's scripts probably can run on another server as well, > maybe even on SF's shell servers. Or the whole construct of generating > those pages can be reworked to be more obvious, easier to test and > so easier to improve. First thing which wasn't that obvious for someone outstanding is, that the whole stuff is actually under version control since it's birth, the directory just needed to be checked out: https://geany-plugins.svn.sourceforge.net/svnroot/geany-plugins/www/staging I guess there weren't that much people who actually knew that. Maybe this one is easier to find: https://github.com/dmaphy/plugins.geany.org Improvement to that script-bundle are welcome anytime. About reworking the whole concept: I'd personally love the idea of the GitHub pages stuff, we maybe could do something on basis of that. There also were some nice ideas on IRC a few minutes ago which you guys maybe like to discuss here. My suggestion is to start a rework with or after the Geany-Plugins 0.21 release. Regards, Dominic -- Dominic Hopf http://dominichopf.de/ Key Fingerprint: A7DF C4FC 07AE 4DDC 5CA0 BD93 AAB0 6019 CA7D 868D signature.asc Description: This is a digitally signed message part ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] Plugins README / web pages
Am Montag, den 10.10.2011, 13:55 +0400 schrieb Alexander Petukhov: > By the way, can I gain more control on READMEs on a web-site to be > able to modify and then upload and see the result instantly. > I was told Dominic maintains this task now. It's not my servers, so I'm not able to decide this. Pinging me on IRC (dmaphy) or Jabber (dma...@jabber.org) maybe is an alternative for that, even if no very good alternative. Regards, Dominic -- Dominic Hopf http://dominichopf.de/ Key Fingerprint: A7DF C4FC 07AE 4DDC 5CA0 BD93 AAB0 6019 CA7D 868D signature.asc Description: This is a digitally signed message part ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] Git switch (for real) (was: Re: geany on github; why not?)
Am Montag, den 03.10.2011, 17:28 +0200 schrieb Colomban Wendling: > Apart that I don't mind, both have the necessary stuff, and Gitorious > is more "free as in freedom". Exactly the reason why I'd personally prefer Gitorous over Github. :) Regards, Dominic -- Dominic Hopf http://dominichopf.de/ Key Fingerprint: A7DF C4FC 07AE 4DDC 5CA0 BD93 AAB0 6019 CA7D 868D signature.asc Description: This is a digitally signed message part ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] Geany-Plugins 0.21: Release plan
Am Mittwoch, den 24.08.2011, 07:45 +0200 schrieb Hans Alves: > One of your problems is a multiple definition of the functions in > geanypg/src/helper_functions.c apparently you still have > geanypg/src/aux.c or .o on your system a couple of revisions ago i > changed aux.c filename to helper_functions.c if you still have aux.c > something went wrong with svn, you should remove it. If it's only > aux.o > do a make clean before building. You actually pointed out a bug in my automatic plugin build script: http://nopaste.geany.org/pastebin.php?diff=m79cc3d3e Thanks! -- Dominic Hopf http://dominichopf.de/ Key Fingerprint: A7DF C4FC 07AE 4DDC 5CA0 BD93 AAB0 6019 CA7D 868D signature.asc Description: This is a digitally signed message part ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] Geany-Plugins 0.21: Release plan
Am Dienstag, den 23.08.2011, 11:47 +0200 schrieb Frank Lanitz: > Hi plugin developers, > > As we discussed a release for Geany 0.21 around October, 1st I'm > thinking also that it would make sense to do a geany-plugins release > around this time. Unfortunately I'm not sure, beside the string freeze > and translation stuff, which goals need to be matched until release. > What do you think? The project at least should successfully build. At present it doesn't, it seems, see attached output. Regards, Dominic -- Dominic Hopf http://dominichopf.de/ Key Fingerprint: A7DF C4FC 07AE 4DDC 5CA0 BD93 AAB0 6019 CA7D 868D output.txt.gz Description: GNU Zip compressed data signature.asc Description: This is a digitally signed message part ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] [PATCH] PHP 5.4 - new keywords
Am Donnerstag, den 21.07.2011, 19:48 -0300 schrieb Felipe Pena: > Hi devs, > Attached is a patch adding two new keywords (related to PHP 5.4): > "insteadof", "trait". Applied with SVN rev 5867. Thanks for the patch. :) Regards, Dominic -- Dominic Hopf http://dominichopf.de/ Key Fingerprint: A7DF C4FC 07AE 4DDC 5CA0 BD93 AAB0 6019 CA7D 868D signature.asc Description: This is a digitally signed message part ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] hex mode
Am Donnerstag, den 14.04.2011, 22:29 +0200 schrieb Liviu Andronic: > And a bit more OT, Geany refuses to force-open a PDF file. Nano, for > example, opens the PDF. Is it normal? This is intended behavior as far as I know, yes. Regards, Dominic -- Dominic Hopf http://dominichopf.de/ Key Fingerprint: A7DF C4FC 07AE 4DDC 5CA0 BD93 AAB0 6019 CA7D 868D signature.asc Description: This is a digitally signed message part ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] geany-newsletter: License of newsletter
Am Freitag, den 08.04.2011, 18:28 +0200 schrieb Thomas Martitz: > Am 08.04.2011 18:18, schrieb Frank Lanitz: > > Hi people, > > > > I just want to ask about which license we shall use for the newsletter > > in future. I'd like to prefer to put it under terms of one of the > > CC-family licenses. CC-BY (by = Geany Newsletter Team) would fit most > > IMHO. What's your opinion? > > I never heard of licenses for newsletters. Me neither. -- Dominic Hopf http://dominichopf.de/ Key Fingerprint: A7DF C4FC 07AE 4DDC 5CA0 BD93 AAB0 6019 CA7D 868D signature.asc Description: This is a digitally signed message part ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] A few fixes for codenav, geanygdb, geanyinsertnum and geanylatex
Am Mittwoch, den 23.02.2011, 19:32 +0100 schrieb Colomban Wendling: > [./geanygdb/src/gdb-io-frame.c:186]: (error) Possible null pointer > dereference: lv Applied. Thanks. :) -- Dominic Hopf http://dominichopf.de/ Key Fingerprint: A7DF C4FC 07AE 4DDC 5CA0 BD93 AAB0 6019 CA7D 868D signature.asc Description: This is a digitally signed message part ___ Geany-devel mailing list Geany-devel@uvena.de http://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] Filter in the File Browser Plugin
Am Samstag, den 19.02.2011, 18:04 +0400 schrieb Grigory Javadyan: > Hi, > > > I recently started using Geany and noticed that the file browser > plugin lacks the ability to include multiple patterns into the filter. > For example, I can't set the filter up so that the plugin displays > *.cpp and *.h files, but not *.o files. I browsed through the code of > the plugin and found out that it simply uses g_pattern_match. > However, it's not too difficult to alter the code so that it supports > multiple patterns. I would like to do that. Please let me know if this > feature is needed. If it is, I'll start working on it. I'd appreciate such a feature, yep. :) -- Dominic Hopf http://dominichopf.de/ Key Fingerprint: A7DF C4FC 07AE 4DDC 5CA0 BD93 AAB0 6019 CA7D 868D signature.asc Description: This is a digitally signed message part ___ Geany-devel mailing list Geany-devel@uvena.de http://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] plugins.geany.org now updating automatically via cronjob
Am Samstag, den 12.02.2011, 14:19 +0100 schrieb Enrico Tröger: > True. > My suggestion was based on your statement, the README content should > match the released plugin version. To avoid confusion: I was talking about the informations contained in the README file, not the content. I don't want any plugin developer to fit his README file 1:1 with the released file. I just was suggesting to be consistent with the behavior the actual released plugin behaves. And this is just a suggestion, no requirement. It's still up to the plugin developer how he maintains his README. :) > Maybe this isn't necessary at all. I don't see READMEs as > the documentation of a plugin and so the README should be as up to date > as necessary and should not match a months old release state. > Just my 2cents. Of course. Consistency with the described behavior and the up-to-dateness don't exclude each other. :) Regards, Dominic -- Dominic Hopf http://dominichopf.de/ Key Fingerprint: A7DF C4FC 07AE 4DDC 5CA0 BD93 AAB0 6019 CA7D 868D signature.asc Description: This is a digitally signed message part ___ Geany-devel mailing list Geany-devel@uvena.de http://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] plugins.geany.org now updating automatically via cronjob
Am Samstag, den 12.02.2011, 12:24 +0100 schrieb Enrico Tröger: > On Sat, 12 Feb 2011 03:05:44 +0100, Frank wrote: > > >On Sat, 12 Feb 2011 00:04:32 +0100 > >Dominic Hopf wrote: > > > >> Am Freitag, den 11.02.2011, 23:56 +0100 schrieb Dominic Hopf: > >> > In detail, this means the descriptions for your plugins at > >> > plugins.geany.org, which are generated from your README files, will > >> > be updated once per day at 04:05 UTC. > >> > >> Maybe it would be also a good idea to increase the frequency to every > >> hour or so? Tell me what you think. > > Not sure whether every hour is really necessary. It's just that it > probably takes some server resources...but to be honest I didn't know > what the script does so I can't judge on that at this point. > > But as you said in your first mail, plugin authors should keep the > information in the READMEs consistent with the released version. > This doesn't make much sense to me. The README in SVN should reflect > the latest development changes. > But I agree to have a version online at the website which fits the > released version. So, IMO it's better to adjust your script to generate > HTML from the tagged READMEs. And this is just necessary after a > release, not every hour. > What do you think? I wouldn't generate the website from tagged releases, since they shouldn't be changed after the release from my point of view. Plugin developers may want to improve other things on their README files, in special when seeing something isn't displayed that optimal on the website, I think it is a more good idea to generate the website from trunk. But this would imply, the informations contained in the README files are consistent with the released tarballs. Otherwise, if we generate the website from tagged releases, this would mean something would be fucked up until the next release, in the worst case. few other thoughts to this topic: * have an additional README.stable * and maybe generate an additional plugins.geany.org/svn/ Regards, Dominic -- Dominic Hopf http://dominichopf.de/ Key Fingerprint: A7DF C4FC 07AE 4DDC 5CA0 BD93 AAB0 6019 CA7D 868D signature.asc Description: This is a digitally signed message part ___ Geany-devel mailing list Geany-devel@uvena.de http://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] plugins.geany.org now updating automatically via cronjob
Am Samstag, den 12.02.2011, 03:05 +0100 schrieb Frank Lanitz: > On Sat, 12 Feb 2011 00:04:32 +0100 > Dominic Hopf wrote: > > > Am Freitag, den 11.02.2011, 23:56 +0100 schrieb Dominic Hopf: > > > In detail, this means the descriptions for your plugins at > > > plugins.geany.org, which are generated from your README files, will > > > be updated once per day at 04:05 UTC. > > > > Maybe it would be also a good idea to increase the frequency to every > > hour or so? Tell me what you think. > > I'm thinking about a post-commit hook which is deploying it after > tagging (or something like this) Guess that won't be possible, unfortunately. Post-commit-hooks have to be implemented on the SVN repository as far as I know... not that I'd knew we have access to the server-side repository at SourceForge. Regards, Dominic -- Dominic Hopf http://dominichopf.de/ Key Fingerprint: A7DF C4FC 07AE 4DDC 5CA0 BD93 AAB0 6019 CA7D 868D signature.asc Description: This is a digitally signed message part ___ Geany-devel mailing list Geany-devel@uvena.de http://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] plugins.geany.org now updating automatically via cronjob
Am Freitag, den 11.02.2011, 23:56 +0100 schrieb Dominic Hopf: > In detail, this means the descriptions for your plugins at > plugins.geany.org, which are generated from your README files, will be > updated once per day at 04:05 UTC. Maybe it would be also a good idea to increase the frequency to every hour or so? Tell me what you think. Regards, Dominic -- Dominic Hopf http://dominichopf.de/ Key Fingerprint: A7DF C4FC 07AE 4DDC 5CA0 BD93 AAB0 6019 CA7D 868D signature.asc Description: This is a digitally signed message part ___ Geany-devel mailing list Geany-devel@uvena.de http://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
[Geany-devel] plugins.geany.org now updating automatically via cronjob
Hey guys, since there are some rewrite rules which are just working with Apache, the preview site at plugins2.geany.org is broken because it is running on lighttpd and the rules are incompatible, unfortunately. This actually was the site, a cronjob updated once per day. This doesn't make much sense, thus I enabled the push to live for the cronjob, finally. It took a lot if time to do so, I know. Sorry for that. In detail, this means the descriptions for your plugins at plugins.geany.org, which are generated from your README files, will be updated once per day at 04:05 UTC. It would make sense to keep the informations of the README files consistent with the behavior of the plugins the released tarballs actually contain. Feel free to suggest improvements and give feedback if you like this or not. :) Regards, Dominic -- Dominic Hopf http://dominichopf.de/ Key Fingerprint: A7DF C4FC 07AE 4DDC 5CA0 BD93 AAB0 6019 CA7D 868D signature.asc Description: This is a digitally signed message part ___ Geany-devel mailing list Geany-devel@uvena.de http://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] svn export results in svn: Inconsistent line ending style
Am Donnerstag, den 10.02.2011, 12:43 +1100 schrieb Lex Trotman: > On 10 February 2011 12:01, Dominic Hopf wrote: > > Hey guys, > > > > I just wanted to build a new snapshot of Geany from SVN. For this, I'm > > usually going to svn export the current working copy from trunk into > > another directory (to be clean of .svn subdirs). This time I got a bit > > weird output I don't understand yet: > > > > % LANG=C svn export geany geany-0.21 > > svn: Inconsistent line ending style > > Yeah, if Enrico muttered the right incantations over the repository > SVN server will provide files with line endings appropriate to the > client platform. > > maybe try --native-eol CRLF (or whatever matches your platform) > > Also maybe you have changes in your tree that are not line ending consistent. A svn export geany geany-0.21 --native-eol LF did the job. Now exports don't abort anymore, even with leaving the --native-eol option again. Weird stuff. Thanks Lex. -- Dominic Hopf http://dominichopf.de/ Key Fingerprint: A7DF C4FC 07AE 4DDC 5CA0 BD93 AAB0 6019 CA7D 868D signature.asc Description: This is a digitally signed message part ___ Geany-devel mailing list Geany-devel@uvena.de http://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
[Geany-devel] svn export results in svn: Inconsistent line ending style
Hey guys, I just wanted to build a new snapshot of Geany from SVN. For this, I'm usually going to svn export the current working copy from trunk into another directory (to be clean of .svn subdirs). This time I got a bit weird output I don't understand yet: % LANG=C svn export geany geany-0.21 svn: Inconsistent line ending style The exports seems to break and doesn't finish successfully. Is this something where I should search the reason locally in my SVN installation or is SVN that clever to know of the source code files of Geany? (SVN rev is 5542) Regards, Dominic -- Dominic Hopf http://dominichopf.de/ Key Fingerprint: A7DF C4FC 07AE 4DDC 5CA0 BD93 AAB0 6019 CA7D 868D signature.asc Description: This is a digitally signed message part ___ Geany-devel mailing list Geany-devel@uvena.de http://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] Small errors/memory leaks on a few plugins
Am Sonntag, den 06.02.2011, 16:55 +0100 schrieb Enrico Tröger: > Hey guys, > > out of fun, I just run 'cppcheck', a tool for static C code analysis, > on the Geany code as well as on the components of the Geany-Plugins > project. > > For Geany, it didn't find any errors: yay! > > For the Geany-Plugins, the found errors are attached to this mail. > > There is nothing critical, mostly memory leaks in codenav, geanygdb, > geanylatex and pretty-printer which should be easy to fix. > > I did not checked whether the reported errors are really errors or if > there is maybe a false positive. I leave this to the plugin > maintainers. For geanygdb the issues should be fixed. Regards, Dominic -- Dominic Hopf http://dominichopf.de/ Key Fingerprint: A7DF C4FC 07AE 4DDC 5CA0 BD93 AAB0 6019 CA7D 868D signature.asc Description: This is a digitally signed message part ___ Geany-devel mailing list Geany-devel@uvena.de http://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] debugger plugin
Am Sonntag, den 30.01.2011, 14:09 +0100 schrieb Enrico Tröger: > On Tue, 25 Jan 2011 14:50:17 +0300, Александр wrote: > > >Thanks Thomas, > > > >I'll try to look at crash on non-debug modules soon, though i didn't > >have this bug when I tried to debug a plugin itself i.e. run geany as > >a debug target. > > > >To Geany-plugins mainteiners: how can i start to move source code to > >geany-plugins svn? > > First, tell us your Sourceforge username, so we can give you SVN write > access. Then just commit your plugin code into > trunk/geany-plugins/debugger (or whatever name you'll choose). > Afterwards, you/we need to update the autotools and Waf-based build > systems to get your plugin built. But this is one of the last steps. > > > >Regading plugin name, does anybody mind if the name will be simply > >"debugger"? Though GeanyGDB has this title exposed in plugins dialog, > >no such name is presented as a real plugin name. > > It definitely will confuse users but I don't know of anything better so > far too :(. > Can it replace the geanygdb plugin at some time? I actually didn't found time yet to have a look at this new one, but GeanyGDB is quiet unmaintained at present and didn't change since almost a year. Of course I'd appreciate any support or patches, but if this new one does the job more better, than I'd also be fine with replacing GeanyGDB. Regards, Dominic -- Dominic Hopf http://dominichopf.de/ Key Fingerprint: A7DF C4FC 07AE 4DDC 5CA0 BD93 AAB0 6019 CA7D 868D signature.asc Description: This is a digitally signed message part ___ Geany-devel mailing list Geany-devel@uvena.de http://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
[Geany-devel] Improving usability and handling for Geany-Plugins
Hi together, in special plugin developers ;) We currently are in the situation, that a user just sees the Geany-Plugins version when reporting bugs [1] but in the plugin manager in Geany just sees the version of the plugin itself. This might be confusing when the user doesn't remember which version of Geany-Plugins he actually has installed. Some plugins already have the same version as Geany-Plugins. This isn't that good anymore when a new plugin arrives in the Geany-Plugins project. Imagine before joining Geany-Plugins the version was 0.0.3 and after joining it directly jumps to 0.21. Here are some alternate suggestions: * change the version string for each plugin, e.g. 0.0.1-gp0.20 * change the text in the description (something like "this is foobar 0.0.1 brought to you by Geany-Plugins 0.20") They additionally would fix another issue which will come up the more plugins Geany will get: Differing between the "provider" of the plugin - was this Geany-Plugins or was it delivered with Geany, or is it a completely other third-party plugin? Maybe someone of you has also suggestions or thoughts on this, please let us know. :) Regards, Dominic [1] https://sourceforge.net/tracker/?group_id=222729&atid=1056532 -- Dominic Hopf http://dominichopf.de/ Key Fingerprint: A7DF C4FC 07AE 4DDC 5CA0 BD93 AAB0 6019 CA7D 868D signature.asc Description: This is a digitally signed message part ___ Geany-devel mailing list Geany-devel@uvena.de http://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] [RFC] Releasing Geany-Plugins
Am Sonntag, den 16.01.2011, 13:37 +0100 schrieb Frank Lanitz: > On Sat, 15 Jan 2011 00:57:12 +0100 > Dominic Hopf wrote: > > > Hey guys, > > > > while talking with hyperair on IRC about the Geany-Plugins release > > this week, we realized that there we're some small things which could > > have been better and improved in the release process. I suggested to > > write the steps down which have to be done and the result is... call > > it "check list", "guidelines" or "piece of text" or $somewhat > > > > Check it out here and feel free to improve: > > http://typewith.me/i1NkZGwVq5 > > > > The idea is to add this text to SVN repository of Geany--Plugins as > > soon as everyone is okay with it. > > Maybe we could also add some part for hacking a plugin. Some docu is > already avaialble at e.g. > http://www.geany.org/manual/reference/howto.html but still some parts > e.g. of integrating with build system, GCC-compiler flags for > debugging, gdb, might be missing. Then we'd call the document rather something like "Geany-Plugins guidelines" or "Geany-Plugins HowTo", because it wouldn't just to the releasing process, of course. I appreciate any improvement, feel free to just add it to the text there. I prepared a new paragraph where it may could be placed then. :) Regards, Dominic -- Dominic Hopf http://dominichopf.de/ Key Fingerprint: A7DF C4FC 07AE 4DDC 5CA0 BD93 AAB0 6019 CA7D 868D signature.asc Description: This is a digitally signed message part ___ Geany-devel mailing list Geany-devel@uvena.de http://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
[Geany-devel] [RFC] Releasing Geany-Plugins
Hey guys, while talking with hyperair on IRC about the Geany-Plugins release this week, we realized that there we're some small things which could have been better and improved in the release process. I suggested to write the steps down which have to be done and the result is... call it "check list", "guidelines" or "piece of text" or $somewhat Check it out here and feel free to improve: http://typewith.me/i1NkZGwVq5 The idea is to add this text to SVN repository of Geany--Plugins as soon as everyone is okay with it. Let me know if you like it. Regards, Dominic -- Dominic Hopf http://dominichopf.de/ Key Fingerprint: A7DF C4FC 07AE 4DDC 5CA0 BD93 AAB0 6019 CA7D 868D signature.asc Description: This is a digitally signed message part ___ Geany-devel mailing list Geany-devel@uvena.de http://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] debugger plugin
Am Freitag, den 07.01.2011, 17:24 +0100 schrieb Frank Lanitz: > Am 07.01.2011 17:02, schrieb Colomban Wendling: > > Le 07/01/2011 16:41, Frank Lanitz a écrit : > >> Am 07.01.2011 15:17, schrieb Alexander Petukhov: > >>> Hello, everybody. > >>> > >>> My name is Alexander, i'm a software developer from St.Petersburg, Russia. > >>> I started to use Geany at my job, mostly for C++ development, and only > >>> feature I was not satisfied with > >>> was debuggers support. > >>> I looked at the existing GDB plugin but it's seemed a little bit unusual > >>> for me, > >>> and next I thought about multiple debuggers support in one plugin. > >>> So I started to develop my own plugin with the foregoing in mind: > >>> - more VS, Netbeans,... likely GUI > >>> - multiple debuggers support > >>> > >>> Now i have GDB working more or less enough for using, and feel > >>> like I need some feedback. > >>> (I started to work on bashbd backend, but faced some problems and decided > >>> to postpone it, > >>> until GDB and general features will work well). > >>> > >>> So, project adress at SF is https://sourceforge.net/projects/geanydbg/ > >>> Also I've prepared a little page with a description - > >>> http://geanydbg.sourceforge.net/walkthrough.htm > >>> > >>> Waiting four your opinions and feedbacks. > >> Just a general: Maybe we should think about renaming as the 'original' > >> one already is called geanydbg[1] > > AFAIK (and as far as I can see) the original is geanygdb and Alexander's > > one is geanydbg. OK, it's a bit confusing, but it's at least not the same ^^ > > But I agree, changing the name to something more different would be > > better I think. > Oh You are right. I'm sorry. > But obviously its a good sign for changing :D geanygdb geanydbg externdbg ... and I think I remember another plugin which earlier was called geanydbg. Could be that's what externdbg now is and it got renamed right to avoid such confusion for the users... I also vote to rename the plugin. Regards, Dominic -- Dominic Hopf http://dominichopf.de/ Key Fingerprint: A7DF C4FC 07AE 4DDC 5CA0 BD93 AAB0 6019 CA7D 868D signature.asc Description: This is a digitally signed message part ___ Geany-devel mailing list Geany-devel@uvena.de http://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] scintilla rectangle selection change & 0.20 release
Am Montag, den 22.11.2010, 13:03 + schrieb Nick Treleaven: > On Sun, 21 Nov 2010 18:29:36 +0100 > Enrico Tröger wrote: > > > >Do we plan to update scintilla anytime soon? If not, would it be > > > > Nick? > > Any release plans soon? > > Yes, I think we could make the 0.20 release soon. If there are no > i18n string changes to add we could start the string freeze in a few > days maybe? > > > I just updated Scintilla in my working copy, adopted the new layout: > > > > geany > > - ... > > - plugins > > - scintilla > >- gtk > >- include > >- lexers > >- lexlib > >- src > > - src > > > > and adjusted the Waf based build system for the change. > > I didn't test it much so far but it seems fine. > > > > What next? > > Either we push into trunk and see how it works or in case we are close > > to a release, I'd push it into a branch for the curious people. > > I think it would be best to put it in an 'unstable' branch. Last time > we updated Scintilla just before the 0.19 release it introduced > scrolling bugs. I tend to suggest this right the "inverse way", create a stable branch to work towards the 0.20 release and continue the "unstable" work in trunk... Regards, Dominic -- Dominic Hopf http://dominichopf.de/ Key Fingerprint: A7DF C4FC 07AE 4DDC 5CA0 BD93 AAB0 6019 CA7D 868D signature.asc Description: This is a digitally signed message part ___ Geany-devel mailing list Geany-devel@uvena.de http://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] (no subject)
Am Donnerstag, den 28.10.2010, 20:45 +0200 schrieb Frank Lanitz: > On Thu, 28 Oct 2010 11:24:26 -0700 (PDT) > Sergey Terlemezyan wrote: > > > Could you tell me how can I add my own plugin to the available > > plugins list? > > If you are talking about plugins.geany.org can you give some more > details about the plugin? Once we do have this I guess we can add > something. Just in case we're really talking about the website plugins.geany.org here, I'd also recommend to have a look at http://plugins.geany.org/README.html. Regards, Dominic -- Dominic Hopf http://dominichopf.de/ Key Fingerprint: A7DF C4FC 07AE 4DDC 5CA0 BD93 AAB0 6019 CA7D 868D signature.asc Description: This is a digitally signed message part ___ Geany-devel mailing list Geany-devel@uvena.de http://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] using ctrl+c in vte
Am Montag, den 25.10.2010, 21:31 +0200 schrieb Liviu Andronic: > Dear all > Currently it is not possible to use ctrl+c to terminate a program > started in the virtual terminal emulator. Is this an intended omission > in the integration with Geany or perhaps some VTE limitation? > > I'm asking since I would find useful being able to stop code execution > while working in R. Regards > Liviu Hi Liviu, have you checked the preferences for VTE? I think the 'Override Geany keybindings' option could be what you're searching for. Having this checked Ctrl-C works fine for me. :) Regards, Dominic -- Dominic Hopf http://dominichopf.de/ Key Fingerprint: A7DF C4FC 07AE 4DDC 5CA0 BD93 AAB0 6019 CA7D 868D signature.asc Description: This is a digitally signed message part ___ Geany-devel mailing list Geany-devel@uvena.de http://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] plugins.geany.org beauty urls / plugin directories lying around in htdocs/
Am Sonntag, den 17.10.2010, 02:19 +0200 schrieb Frank Lanitz: > On Sat, 16 Oct 2010 21:17:39 +0200 > Dominic Hopf wrote: > > > The question for those plugins having a directory lying around there > > is: Do you still need that directory or would it be possible to > > delete it and remove the exclude from the rewrite rules? Then your > > plugin would also have the "beauty URL". > > > > Requestion ist, where are these folder located? In the document root of the plugins.geany.org site, which actually is on sourceforge: /home/groups/g/ge/geany-plugins/htdocs/. But wait... with SVN rev 1663 I slightly modified the rewrite rules again to show up some possibilities which work at present: http://plugins.geany.org/geanygdb.html http://plugins.geany.org/geanygdb http://plugins.geany.org/site/geanygdb.html http://plugins.geany.org/site/geanygdb http://plugins.geany.org/index.php?site=geanygdb (this one is actually the default without any rewrite) Yes, this maybe looks a bit weird. So the regexes are. For those with the "site" in the URL, it wouldn't be necessary to delete folders anymore, even if Enrico already did so for the addons and spellcheck plugin (thanks, anyway). Thus, maybe someone of you wants to drop his 2 cents about this. And yes, I know, mod_rewrite is evil. :) Best Regards, Dominic -- Dominic Hopf http://dominichopf.de/ Key Fingerprint: A7DF C4FC 07AE 4DDC 5CA0 BD93 AAB0 6019 CA7D 868D signature.asc Description: This is a digitally signed message part ___ Geany-devel mailing list Geany-devel@uvena.de http://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
[Geany-devel] plugins.geany.org beauty urls / plugin directories lying around in htdocs/
Hi all, I just added a new "feature" to the plugins.geany.org website. It is some rewrite rules in an .htaccess file which allow to call specific pages like this: http://plugins.geany.org/downloads or http://plugins.geany.org/geanygdb just as examples. Unfortunately, this will not work for all plugins, since there are some directories lying around in htdocs/: $ ls -l total 96 drwxr-sr-x 2 209508 geany-plugins 1024 Jan 17 2010 addons/ drwxrwsr-x 2 dmaphy geany-plugins 2048 Oct 16 04:05 content/ -rw-rw-r-- 1 dmaphy geany-plugins 4286 Jul 31 16:17 favicon.ico drwxrwsr-x 2 dmaphy geany-plugins 2048 Jul 31 21:46 geany-plugins/ drwxr-sr-x 2 137082 geany-plugins 1024 Sep 15 2008 geanydoc/ drwxrwsr-x 2 dmaphy geany-plugins 1024 Jul 31 20:10 geanylua/ drwxr-sr-x 2 137082 geany-plugins 1024 Sep 15 2008 geanyprj/ drwxr-sr-x 2 137082 geany-plugins 1024 Sep 15 2008 geanyvc/ drwxrwsr-x 2 dmaphy geany-plugins 1024 Jul 31 16:17 images/ -rw-rw-r-- 1 dmaphy geany-plugins 2606 Oct 8 23:14 index.php drwxr-sr-x 2 209508 geany-plugins 2048 Jan 17 2010 spellcheck/ drwxrwsr-x 2 dmaphy geany-plugins 1024 Sep 4 22:13 stylesheets/ I excluded those plugins with an existing directory from the rewrite. Thus, e.g. for the geanyvc plugin, the described behaviour will not work: http://plugins.geany.org/geanyvc/ The question for those plugins having a directory lying around there is: Do you still need that directory or would it be possible to delete it and remove the exclude from the rewrite rules? Then your plugin would also have the "beauty URL". Thanks very much in advance for your feedback and your support. :) Best Regards, Dominic -- Dominic Hopf http://dominichopf.de/ Key Fingerprint: A7DF C4FC 07AE 4DDC 5CA0 BD93 AAB0 6019 CA7D 868D signature.asc Description: This is a digitally signed message part ___ Geany-devel mailing list Geany-devel@uvena.de http://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] File type icons?
Am Donnerstag, den 14.10.2010, 16:36 +0200 schrieb Colomban Wendling: > Hi, > > I realized that in the "documents" sidebar each and every files have an > icon, but they all have the same, no matter what. I had a little time > and I decided to play a bit with the idea of having file-type based icons. > > Such icons could be displayed at a few places: > > 1) In the Documents sidebar: there is already icons and it would > probably ease to find a particular item (if different filetypes are > mixed, of course). Anyway I think it's better to have the "right" icons > rather than always using the same. (capture joined) > > 2) In the document notebook popup. This will perhaps ease finding the > item, but perhaps adds clutter. Not sure. (capture joined) > > 3) In the tab title, like GEdit does. I think this one is a bad idea > since it is probably useless and only use a little more space. 4) In file browser and tree browser plugin, which maybe could use functions provided by Geany for showing those icons. I short: I love this idea! :) Regards, Dominic -- Dominic Hopf http://dominichopf.de/ Key Fingerprint: A7DF C4FC 07AE 4DDC 5CA0 BD93 AAB0 6019 CA7D 868D signature.asc Description: This is a digitally signed message part ___ Geany-devel mailing list Geany-devel@uvena.de http://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
[Geany-devel] [ANN] new plugins.geany.org
Hi together, not sure if I ever "officially" announced, there is a new plugins.geany.org website. There were lot of things to do since my movement to Hamburg in July, so it may be I missed that. ;) Since it is already online since a few weeks now, most of you most likely already noticed it. - I even already got feedback via the SourceForge bug tracker where Enrico added a new section for the website. :) However, I just found a few minutes time to write a small blog post about it which may answers some unclear questions or anything else [1]. I'd appreciate any feedback to the site or even the blog post. Although it maybe takes long again until I get to fix reported issues. ;) Best Regards, Dominic [1] http://dmaphy.blogspot.com/2010/10/geany-plugins-fast-and-lightweight.html -- Dominic Hopf http://dominichopf.de/ Key Fingerprint: A7DF C4FC 07AE 4DDC 5CA0 BD93 AAB0 6019 CA7D 868D signature.asc Description: This is a digitally signed message part ___ Geany-devel mailing list Geany-devel@uvena.de http://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] Heads up Plugin developers, there are README files missing
Am Dienstag, den 17.08.2010, 02:52 +0200 schrieb Colomban Wendling: > Hi Dominic, > > Le 16/08/2010 20:54, Dominic Hopf a écrit : > > Time to let you know there is happening something strange guys. There is > > a cronjob running, generating the content on http://plugins2.geany.org/ > > from your README files. > > > > Below is the output of the shell script, important there is, there are > > some plugins not providing a README or it's not written in > > reStructuredText. > > > > Well, I don't want you to write those, since there are other ways to get > > your plugin to that page, but if there would be a README written in > > ReST, it would make things a lot easier... ;) > > Should be fine for GeanyGenDoc now :) > BTW, I have a full documentation in geanygendoc/docs/manual.rst, not > sure which of this or the README should go in there... do as you think > it's better. I'll have a deeper look on this next week, thanks for pointing on that. :) Dominic -- Dominic Hopf http://dominichopf.de/ Key Fingerprint: A7DF C4FC 07AE 4DDC 5CA0 BD93 AAB0 6019 CA7D 868D ___ Geany-devel mailing list Geany-devel@uvena.de http://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] Heads up Plugin developers, there are README files missing
Am Dienstag, den 17.08.2010, 20:11 +0300 schrieb Dimitar Zhekov: > On Mon, 16 Aug 2010 23:22:51 +0200 > Dominic Hopf wrote: > > > > Can you provide the ReST warnings for the plugins which have been > > > compiled successful, but with warnings? > > > > Those warnings actually are there everytime, but you can find attached a > > full output of the shell script. > > There seems to be a warning for every parsed ReST README, but the > attached output still does not contain any warnings. Then it seems to be an issue with parsing the exit codes in my script. I'll have a deeper look into this next week, thanks for pointing me to that. :) Regards, Dominic -- Dominic Hopf http://dominichopf.de/ Key Fingerprint: A7DF C4FC 07AE 4DDC 5CA0 BD93 AAB0 6019 CA7D 868D ___ Geany-devel mailing list Geany-devel@uvena.de http://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] Heads up Plugin developers, there are README files missing
Am Montag, den 16.08.2010, 22:23 +0200 schrieb Frank Lanitz: > On Mon, 16 Aug 2010 20:54:26 +0200 > Dominic Hopf wrote: > > > Below is the output of the shell script, important there is, there are > > some plugins not providing a README or it's not written in > > reStructuredText. > > > > Well, I don't want you to write those, since there are other ways to > > get your plugin to that page, but if there would be a README written > > in ReST, it would make things a lot easier... ;) > > Can you provide the ReST warnings for the plugins which have been > compiled successful, but with warnings? Those warnings actually are there everytime, but you can find attached a full output of the shell script. The source of the script (and anything else concerning that website) [1] is also available by the way. Regards, Dominic [1] http://geany-plugins.svn.sourceforge.net/viewvc/geany-plugins/www/staging/ -- Dominic Hopf http://dominichopf.de/ Key Fingerprint: A7DF C4FC 07AE 4DDC 5CA0 BD93 AAB0 6019 CA7D 868D output.txt.gz Description: GNU Zip compressed data signature.asc Description: This is a digitally signed message part ___ Geany-devel mailing list Geany-devel@uvena.de http://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
[Geany-devel] Heads up Plugin developers, there are README files missing
Time to let you know there is happening something strange guys. There is a cronjob running, generating the content on http://plugins2.geany.org/ from your README files. Below is the output of the shell script, important there is, there are some plugins not providing a README or it's not written in reStructuredText. Well, I don't want you to write those, since there are other ways to get your plugin to that page, but if there would be a README written in ReST, it would make things a lot easier... ;) Regards, Dominic Weitergeleitete Nachricht > Von: Cron Daemon > An: dma...@uvena.de > Betreff: Cron /home/dmaphy/bin/plugins_cronjob.sh > 2> /dev/null > Datum: Mon, 16 Aug 2010 04:05:09 + (UTC) > > Fetching external item into '/home/dmaphy/plugins.geany.org/geanylua' > External at revision 1508. > > At revision 1508. > /usr/bin/tidy exited with 1. There were warnings, but this is okay. > You maybe should have another look at > /home/dmaphy/plugins.geany.org/content/addons.html yourself.' > > /usr/bin/tidy exited with 1. There were warnings, but this is okay. > You maybe should have another look at > /home/dmaphy/plugins.geany.org/content/codenav.html yourself.' > > /usr/bin/tidy exited with 1. There were warnings, but this is okay. > You maybe should have another look at > /home/dmaphy/plugins.geany.org/content/geanydoc.html yourself.' > > /usr/bin/tidy exited with 1. There were warnings, but this is okay. > You maybe should have another look at > /home/dmaphy/plugins.geany.org/content/geanyextrasel.html yourself.' > > /usr/bin/tidy exited with 1. There were warnings, but this is okay. > You maybe should have another look at > /home/dmaphy/plugins.geany.org/content/geanygdb.html yourself.' > > File /home/dmaphy/geany-plugins/geanygendoc/README not found. > You might want to have a look whats up there. > Copying no-readme-template instead.. > /usr/bin/tidy exited with 1. There were warnings, but this is okay. > You maybe should have another look at > /home/dmaphy/plugins.geany.org/content/geanyinsertnum.html yourself.' > > /usr/bin/tidy exited with 1. There were warnings, but this is okay. > You maybe should have another look at > /home/dmaphy/plugins.geany.org/content/geanylipsum.html yourself.' > > /usr/bin/tidy exited with 1. There were warnings, but this is okay. > You maybe should have another look at > /home/dmaphy/plugins.geany.org/content/geanyprj.html yourself.' > > /usr/bin/tidy exited with 1. There were warnings, but this is okay. > You maybe should have another look at > /home/dmaphy/plugins.geany.org/content/geanyvc.html yourself.' > > File /home/dmaphy/geany-plugins/pretty-printer/README not found. > You might want to have a look whats up there. > Copying no-readme-template instead.. > /usr/bin/tidy exited with 1. There were warnings, but this is okay. > You maybe should have another look at > /home/dmaphy/plugins.geany.org/content/shiftcolumn.html yourself.' > > /usr/bin/tidy exited with 1. There were warnings, but this is okay. > You maybe should have another look at > /home/dmaphy/plugins.geany.org/content/spellcheck.html yourself.' > > File /home/dmaphy/geany-plugins/treebrowser/README not found. > You might want to have a look whats up there. > Copying no-readme-template instead.. > sending incremental file list > ./ > .README.html > content/ > content/addons.html > content/codenav.html > content/geany-plugins-listing.html > content/geanydoc.html > content/geanyextrasel.html > content/geanygdb.html > content/geanygendoc.html > content/geanyinsertnum.html > content/geanylipsum.html > content/geanyprj.html > content/geanyvc.html > content/pretty-printer.html > content/shiftcolumn.html > content/spellcheck.html > content/treebrowser.html > > sent 71862 bytes received 325 bytes 144374.00 bytes/sec > total size is 105487 speedup is 1.46 -- Dominic Hopf http://dominichopf.de/ Key Fingerprint: A7DF C4FC 07AE 4DDC 5CA0 BD93 AAB0 6019 CA7D 868D signature.asc Description: This is a digitally signed message part ___ Geany-devel mailing list Geany-devel@uvena.de http://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] When is the scintilla component going to be updated?
Am Dienstag, den 10.08.2010, 09:02 +1000 schrieb Erik de Castro Lopo: > On top of that myself and others are submitting patches to this > mailing list and not even having them acknowledged by anyone > with SVN commit access. That's just because hard and long work within the week. At least for me, and I guess it's the same for the other guys. You can be sure your patches have been or will be seen, reviewed and most likely also applied. It may just take a bit at present, but I'll promise to better myself. Regards, Dominic -- Dominic Hopf http://dominichopf.de/ Key Fingerprint: A7DF C4FC 07AE 4DDC 5CA0 BD93 AAB0 6019 CA7D 868D signature.asc Description: This is a digitally signed message part ___ Geany-devel mailing list Geany-devel@uvena.de http://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] Script: Generate loadable tag files for Geany
Am Samstag, den 31.07.2010, 18:04 +0200 schrieb Guenther Brunthaler: > > Just a generic hint for the usage of this mailing list: You should start > > new threads for new topics, also if you have another contribution. > > Didn't I?! Seems so. At least it looks like that in my mail client. ;) But well, I had just had a discussion with Enrico on IRC these days about Evolution which may does weird things for me here. Not that important at all I guess, unless there are real big problems of which others may tell me in future.. :) Regards, Dominic -- Dominic Hopf http://dominichopf.de/ Key Fingerprint: A7DF C4FC 07AE 4DDC 5CA0 BD93 AAB0 6019 CA7D 868D signature.asc Description: This is a digitally signed message part ___ Geany-devel mailing list Geany-devel@uvena.de http://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] Script: Generate loadable tag files for Geany
Am Donnerstag, den 29.07.2010, 17:27 +0200 schrieb Guenther Brunthaler: > Hi Lex, > > On 2010-07-29 05:20, Lex Trotman wrote: > > > I better warn you that it might take a while, the developers are a bit > > overloaded with "real" life at the moment. > > No problem, but thanks for the warning anyway. > > Well, here's just the next script: It solves the problem that "geany -g" > can only create tag files for one language at a time, but there may be > multiple source code languages present in a project. > > This script runs "geany -g" with the correct parameters to generate tag > files for all supported languages for the source files encountered in > the current directory tree. You can find this one also at [1], thanks. :) [1] http://www.geany.org/Download/Extras Just a generic hint for the usage of this mailing list: You should start new threads for new topics, also if you have another contribution. Easiest way to do so is, to compose a new mail to geany-devel@uvena.de instead of pressing reply. That's really important for keeping the conversations on the mailing list clearly arranged. :) Regards, Dominic -- Dominic Hopf http://dominichopf.de/ Key Fingerprint: A7DF C4FC 07AE 4DDC 5CA0 BD93 AAB0 6019 CA7D 868D signature.asc Description: This is a digitally signed message part ___ Geany-devel mailing list Geany-devel@uvena.de http://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] Lua Script: Removing stale MRU entries form Geany's config file
Am Donnerstag, den 29.07.2010, 13:20 +1000 schrieb Lex Trotman: > On 29 July 2010 12:48, Guenther Brunthaler wrote: > > Hi Lex, > > > > On 2010-07-29 04:36, Lex Trotman wrote: > > > >> I presume you've found the Geany Lua plugin then :-) > > > > Actually, I had no idea - but thanks for the hint! I'll install it asap! :-) > > > >> The problem with scripts is that they are not portable (Geany runs on > >> *x and *dows) or they create a dependency, in your case on Lua. > > > > Lua also runs ob *x, *doze or any other platform providing a plain > > ANSI-C compiler, because its source code deliberately does not use any > > features outside of those guaranteed by the ANSI-C standard libraries. > > > > But I get your argument, and I agree. It *is* an additional dependency. > > > >> but could probably be put on the extras section of Geany web site for > >> people who are willing to install Lua. > > > > That's all I had hoped for! > > > >> Thats up to the main developers who maintain the web site. > > > > I would feel honored. > > > > I better warn you that it might take a while, the developers are a bit > overloaded with "real" life at the moment. Check this out guys: http://www.geany.org/Download/Extras#scripts Alternatively you can also provide your scripts on a own homepage if you have, Guenther, I would integrate a link to your site then. Just tell me, how you'd like to prefer it. :) Best Regards, Dominic -- Dominic Hopf http://dominichopf.de/ Key Fingerprint: A7DF C4FC 07AE 4DDC 5CA0 BD93 AAB0 6019 CA7D 868D signature.asc Description: This is a digitally signed message part ___ Geany-devel mailing list Geany-devel@uvena.de http://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] Per document tab width
Am Dienstag, den 20.07.2010, 22:20 +0200 schrieb Jiří Techet: > Hi, > > I have one more feature idea and would like to ask if it is something > that others would like to see too before I start implementing it. I'm > working on a project where everyone expresses his personality by using > different tab width for indenting - I have already seen sources with > tab size of 2, 3, 4, 5, 6 and 8 (it's just a matter of time until I > see a source with tab width 7). Of course, these people (or people who > were editing the same source afterwards) also use spaces so sometimes > it happens that I have e.g. tab size set to 4 but the other file I > edit has tab size 2 and it uses spaces too, so what I see is that the > lines using tab get indented less than the lines using spaces. I > usually ignore it, but sometimes the code is so unreadable that I have > to change the tab size. And this is the problem - with geany you have > to do it either per project or globally, it's not possible for a > single file. So I have to switch it in the project settings, look at > the file, and switch it back again because I return back to a file > with different indent size. > > I would propose to have one more entry in the Document menu called > e.g. "Tab size" and placed under "Indent type" with a submenu > containing numbers from 2 to 8 (I hope there is nobody so crazy that > he would use tab for a single char indent or go over 8 characters) > with a radio button selecting the active selection. The user could > change the default tab size of the active document to anything he > wishes. This settings could also be saved into the project/session > file so the files get reloaded with the same tab size settings. What > do you think about this feature? I second the idea of the per-document tab-width. Maybe I would design the menu a bit in another way and provide a small dialog with a text field or spinner where you can setup the tab-width. :) (I guess it's not possible to integrate something like a text field or spinner into a menu?) Best Regards, Dominic -- Dominic Hopf http://dominichopf.de/ Key Fingerprint: A7DF C4FC 07AE 4DDC 5CA0 BD93 AAB0 6019 CA7D 868D signature.asc Description: This is a digitally signed message part ___ Geany-devel mailing list Geany-devel@uvena.de http://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] [geany-plugins] questions about the geany-plugins build system
Am Samstag, den 22.05.2010, 17:17 +0200 schrieb Colomban Wendling:
> Hi everyone,
>
> I'm trying to move my plugin (geanygendoc) into geany-plugins, but I
> have some problems porting the build system -- not used to it.
>
> The thing is that I have data files to install. In my current external
> build system, I install them into $(geany_datadir)/plugins/geanygendoc,
> I think it is probably the good place. Yes, no?
No. I think I remember we discussed this a few month ago. The final
decision was, to have a separate directory (/usr/share/geany-plugins/),
since geany-plugins is another project than geany itself. There already
are some plugins saving their data there, so I'd recommend you to do it
the same.
> Anyway, in the geany-plugins build system, I don't see anything already
> in place to simplify data installation. And even $(datadir) points out
> of a Geany directory, actually $(prefix)/share, which makes me install
> my data in ${prefix}/share/geanygendoc, which is quite ugly IMO. Ah, and
> the second problem which prevents plugin-specific hack is the DATADIR
> defined in vars.build.mk that also points to $(prefix)/share.
> I'd think there should be a $(plugindatadir) variable that points to
> $(prefix)/share/$(plugin), probably defined by a vars.data.mk.
This confuses me a bit. I was sure plugin data should be installed
in /usr/share/geany-plugins/ (and maybe a subdirectory). Maybe I'm wrong
with this, so feel free to correct me.
> Then, what should I do?
>
> Ah, and is there a quick guide explaining how the build system works/how
> to add a plugin to it? I feel the .mk include stuff quite elegant but
> I've some problem to understand it right I think.
For adding your plugin to the geany-plugins project, you may like to
ping hyperair on IRC, he actually maintains such things. You don't have
to do it yourself, IIRC. :)
Regards,
Dominic
--
Dominic Hopf
http://dominichopf.de/
Key Fingerprint:
A7DF C4FC 07AE 4DDC 5CA0 BD93 AAB0 6019 CA7D 868D
signature.asc
Description: Dies ist ein digital signierter Nachrichtenteil
___
Geany-devel mailing list
Geany-devel@uvena.de
http://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] Mircea Hasegan from Romania
Am Donnerstag, den 13.05.2010, 22:26 +0300 schrieb mircea.hase...@gmail.com: > Hi, > > > My name is Mircea Hasegan and I'm from Romania. I've been working for > 3 years in a multinational company as a developer (TCL scripter to be > more exact). > Recently i decided to switch from Windows to Linux. The switch forced > me to find a Linux editor that would meet my needs and expectations. > After many attempts i decided that Geany was the best IDE i could find > and it keeps on exceeding my expectations. Great job! > Yesterday i decided to create a couple of plugins that i needed in > geany (copy full file path to clipboard and clear read-only attributes > from files) because I needed them a lot. > To make a long story short I decided to do my best and try to > contribute to your wonderful project. > I've started coding in C under Linux only recently so my expertise is > not something to brag about, but i'm willing to learn. > Mainly I want to start with reading your code base. Then try to fix > some trivial bugs until I get to understand your code and coding > rules, then advance and help you with more advanced bugs and who > knows, maybe even features. Nice! Welcome to the Geany project! :) -- Dominic Hopf http://dominichopf.de/ Key Fingerprint: A7DF C4FC 07AE 4DDC 5CA0 BD93 AAB0 6019 CA7D 868D signature.asc Description: Dies ist ein digital signierter Nachrichtenteil ___ Geany-devel mailing list Geany-devel@uvena.de http://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] [Geany] Planning the 0.19 release
Am Donnerstag, den 06.05.2010, 16:10 +0100 schrieb Nick Treleaven: > Hi all, > Just a quick mail to let everyone know we're planning to make a Geany > 0.19 release once everything is ready. We're thinking of early June but > this may change ;-) > > So if anyone wants to help test the SVN version, now's a good time to > do so: > http://www.geany.org/Download/SVN > > That link also has nightly tarballs and some binaries too. A little addition: There are also nightly builds for Fedora and Arch, which are not yet mentioned on the above link. See [1] if you like to test those builds as well. I'll update the above mentioned page accordingly soon. Regards, Dominic [1] http://geany.nightlybuilds.org/ -- Dominic Hopf http://dominichopf.de/ Key Fingerprint: A7DF C4FC 07AE 4DDC 5CA0 BD93 AAB0 6019 CA7D 868D signature.asc Description: Dies ist ein digital signierter Nachrichtenteil ___ Geany-devel mailing list Geany-devel@uvena.de http://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] [Patch] - Improve PHP parser (call tips)
Am Samstag, den 17.04.2010, 18:14 +0200 schrieb Enrico Tröger: > On Mon, 8 Mar 2010 23:40:08 +0100, Enrico wrote: > > >On Mon, 8 Mar 2010 12:18:39 +, Nick wrote: > > > >>On Sun, 7 Mar 2010 19:20:37 +0100 > >>Enrico Tröger wrote: > >> > >>> >You put a weird pattern: > >>> >[public|protected|private|static]* > >>> >If you wanted to group, you should use () > >>> > >>> I didn't want to group, we don't need to know the actual modifier, > >>> we just want to allow only this subset. And yes, it was a group > >>> before but there is just no need to. > >> > >>I think Can is right, [] brackets are only for character ranges, not > >>string matching. So () brackets are necessary for matching even when > >>ignoring the group. > > > >Just for the records: > > > >Yup, we talked about that yesterday afterwards on IRC and once he told > >me about that mistake, it was clear. > > I spent a little more time on this again hoping to get it fixed. > In SVN r4828, I adjusted the regular expression for parsing PHP > functions a bit and I think it works now as expected or at least better > than before. All function definitions I tried (with static, > public, ... modifiers and some without and so on) worked and I got the > expected argument list as calltip. > > Though, as muliple times mentioned before, I'm not a PHP guy. Feedback > is welcome. Your pattern seems to work fine now. I've successfully tested different cases as attached and any combination of testcase 1-3 with testcase 4. But, I'd like to point out another issue or rather a feature request. I don't feel it's that important, at least not for me. Also, it maybe is very language-specific for PHP: Since we're obviously writing object-oriented PHP here (because we're using public static anything and so on), it would be nice, if Geany also would parse the so called magic methods [1]. You may noted the __construct method in the attached files. This method is called when a new instance is created as you see in line 24. For completeness Geany should also show calltips in that line when creating the new instance. I can imagine, that this won't be that easy to implement, since Geany would have to have a look into the class which is called (test) and look if a method __construct is there (note it theoretically could be in any place), and if yes, look for the parameters of the __construct method to show the calltip. Well, as I said, not that important, but I at least wanted to let you know there is something. ;) Regards, Dominic [1] http://de3.php.net/manual/en/language.oop5.magic.php -- Dominic Hopf http://dominichopf.de/ Key Fingerprint: A7DF C4FC 07AE 4DDC 5CA0 BD93 AAB0 6019 CA7D 868D <> <> <> <> signature.asc Description: Dies ist ein digital signierter Nachrichtenteil ___ Geany-devel mailing list Geany-devel@uvena.de http://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] newcomer
Am Samstag, den 17.04.2010, 17:43 +0200 schrieb Frank Lanitz: > On Sat, 17 Apr 2010 15:49:30 +0200 > Thomas Martitz wrote: > > > Am 17.04.2010 15:39, schrieb Ariel Haviv: > > > I checked out https://geany.svn.sourceforge.net/svnroot/geany > > > how do i make it locally without installing it instead of my > > > working geany? > > > > $ ./waf confgure && ./waf build > > $ _build_/default/geany > > Or by using the --prefix option of waf or configure run to install it > to some local path. So it might look like > > $ ./waf configure --prefix=/home/user/local && ./waf build && \ > ./waf install You maybe also should consider to use the -c option to use another configuration directory then, just to not confuse your working Geany installation. :) Regards, Dominic -- Dominic Hopf http://dominichopf.de/ Key Fingerprint: A7DF C4FC 07AE 4DDC 5CA0 BD93 AAB0 6019 CA7D 868D signature.asc Description: Dies ist ein digital signierter Nachrichtenteil ___ Geany-devel mailing list Geany-devel@uvena.de http://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] geany layout
Am Samstag, den 10.04.2010, 11:37 +0300 schrieb Enzo Matrix: > > Hello all, > > i want to share one my ide about geany interface layout and if > somebody be interests about it. > > "Append toolbar to menu" is really nice option but i think that my > idea can provide additional minimalism, the idea is simple, the > toolbar can be moved in right of sidebar in top of the editor sheet in > the same level as the tabs of the sidebar and adding one more combobox > for current open files (this will recover tabs). > > > http://img547.imageshack.us/img547/2769/geanynowlayout.png > > http://img412.imageshack.us/img412/3879/geanylayoutmockup.png I actually like the idea, but would suggest some small improvements to it: It always should be possible for the user to decide if he enables or disables features. So disabling of the document tabs should be optional - as it currently is in Geany, see the Interface-tab in the pref-dialog. I'd consider the dropdown-menu in the toolbar as an additional feature which should be optional too (It actually already is, regarding that the toolbar is configurable). Thus, one can disable the document tabs if he wants, and enable the dropdown-menu if he wants. The result would be your suggestion. But if I want to have both, that also would be possible as well as if one would like to stay just with the document tabs. For the idea with the sidebar taking more vertical space: We should think of users with small screen widths and many icons in the toolbar. They maybe wouldn't be visible all at a time. Well, the toolbar is configurable and anytime should be. So the sidebar layout should be configurable for the user too, either in the pref-dialog or as a hidden pref. Best Regards, Dominic -- Dominic Hopf http://dominichopf.de/ Key Fingerprint: A7DF C4FC 07AE 4DDC 5CA0 BD93 AAB0 6019 CA7D 868D signature.asc Description: Dies ist ein digital signierter Nachrichtenteil ___ Geany-devel mailing list Geany-devel@uvena.de http://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] Perl 5.8 vs. 5.10 and default Perl Compile command
Am Dienstag, den 30.03.2010, 23:21 +0200 schrieb Enrico Tröger: > Hey guys, > > I just noticed, newer Perl 5.10 distributions don't have the > B/Bytecode module included anymore. This is what we used in > the past as the default Compile command[1] for the filetype Perl. > The idea was to perform a syntax check this way. > > It seems with 5.10 this module doesn't exist anymore or at least > isn't shipped anymore with the default Perl distribution. > But instead, Perl 5.10 has a -c command line option which also > does a syntax check. I guess this is enough for our needs to be used as > the *default* Compile command. > > Since Perl 5.10 isn't really new anymore, I think we could > change the Compile command. > > But I guess some of you, Nick, Dominic, ... know Perl much better > than me and so can maybe judge a bit better. I think it's okay to change the default compile command to `perl -c "%f"`. I actually already did this for me a few weeks ago. :) Regards, Dominic -- Dominic Hopf http://dominichopf.de/ Key Fingerprint: A7DF C4FC 07AE 4DDC 5CA0 BD93 AAB0 6019 CA7D 868D signature.asc Description: Dies ist ein digital signierter Nachrichtenteil ___ Geany-devel mailing list Geany-devel@uvena.de http://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] [Patch] - Improve PHP parser (call tips)
Am Montag, den 08.03.2010, 12:15 -0800 schrieb Can Koy: > well, who the hell are you? Can, Thomas is contributing to the Geany project for a very long time. As developer as well as a tester. I do not see any reason to ask such questions here. Especially not in that caustically way. > > > Actually, I'm very uncomfortable with my name being > > recorded in that patch's log (r4729). That regex is funny, > > it exhibits an ignorance in the subject and it's not what I > > submitted. So, I demand my name removed from the logs for > > that patch. Maybe it could be, Enrico modified some things on your patch before he commited it, I don't know. If this is the case, he maybe forgot to write the commit message as "based on patch from ..." as he usually does. Well, that could happen to anyone, we're all just humans. So, thanks very much for your understanding. Anyway, Enrico has every right to modify code before applying it onto Geany. As you may have noticed he is one of the main authors of Geany and initiated the project. He still is one of the last ones who decide if code makes it into Geany or not. Geany is Free Software under GPL and any contribution should be too. Thus I see no reason why patches may not be modified before applying them to the project. If the modification is an improvement or not is a technical question which I am not asking for at present. We're open to discuss any technical issue. :) [snip] > > Then please submit a patch to the subversion project to > > enable > > post-editing of commit messages, since this is not possible > > currently. > > > > But honestly, I don't see why this is a big deal. Maybe we > > can > > concentrate on improving Geany and not insisting on minor > > things like this. The fact that your name is mentioned in the commit message can not be undone due to the technical reasons Thomas wrote. I'm afraid you will have to live with that. Please keep in mind that Free Software projects are not mainly intended to make someones name public or not. Such projects are intended to provide good software for the user. - Thus a lot of your patches we're very appreciated. - In most Free Software projects it is the case, that the developers actually are people who have very long working days and do their efforts for the projects in their free time after work. This actually is also the case for the Geany project. I think, a bit of understanding from your side would be appreciated by anyone here. Mistakes can happen to anyone. Regards, Dominic -- Dominic Hopf http://dominichopf.de/ Key Fingerprint: A7DF C4FC 07AE 4DDC 5CA0 BD93 AAB0 6019 CA7D 868D signature.asc Description: Dies ist ein digital signierter Nachrichtenteil ___ Geany-devel mailing list Geany-devel@uvena.de http://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] multiple instance save-settings - Re: Race condition when saving geany.conf
Am Freitag, den 05.03.2010, 16:54 + schrieb Nick Treleaven: > On Tue, 02 Mar 2010 18:50:28 +0100 > Thomas Martitz wrote: > > > >> (If a second instance of geany is run without passing filenames to the > > >> first, -i is implied). > > >> > > >> > > > I really like this idea. It is simple to understand, rather > > > convenient and uniform with the behaviour of "new-instances", i.e., > > > those instances should not touch any global data, either the default > > > session or the settings. > > > > > > > Shouldn't it just bring the existing instance on top without creating a > > new instance? That's what I would expect (i.e. you only get a new > > instance if you use -i). > > The idea is that the user can just click the desktop icon to get a new > window. Raising an existing window is a Window Manager function IMO. That's exactly the behaviour I'd expect too. :) Regards, Dominic -- Dominic Hopf http://dominichopf.de/ Key Fingerprint: A7DF C4FC 07AE 4DDC 5CA0 BD93 AAB0 6019 CA7D 868D signature.asc Description: Dies ist ein digital signierter Nachrichtenteil ___ Geany-devel mailing list Geany-devel@uvena.de http://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] Shift-10 on editor tab
Am Mittwoch, den 03.03.2010, 06:20 -0800 schrieb Can Koy: > - Original Message > > > From: Dominic Hopf > > To: Geany development list > > Sent: Wed, March 3, 2010 3:33:56 PM > > Subject: Re: [Geany-devel] Shift-10 on editor tab > > > > 2010/3/3 Can Koy : > > > Hi, > > > Shift-F10 in an editor tab pops up a nice list of open documents. > > > I'm proposing to change this shortcut to Shift-MenuKey. I can add, > > > instead of > > replace, it if Shift-F10 is too important for you, but replacing is easy. > > What > > do you think? > > > > Hi Can, > > I think Shift+F10 is something like a default behaviour which is written > > down > > in some guidline or anything like that. > > That guide is Gnome HIG, and Shift-F10 is already NOT behaving as stated in > the guide, i.e. show contextual menu (right-click). > > > Also, many users may already know > > Shift+F10 as usual keybinding, so replacing it wouldn't be the best > > solution. > > > > Replacing it (and make Shift-F10 behave like right-click later if required) > would make Geany comply with HIG actually, that's one reason I suggested it. > (Shift-F10 is also clumsy compared to Shift-MenuKey, but that's my opinion.) Well, AFAIK Geany tries to be as best Gnome HIG as it can, so your suggestion should be appreciated. I personally like being as close to a guideline as possible, so a replacement wouldn't be that problem for me. ;) But let's wait what others think about this. :) Regards, Dominic -- Dominic Hopf http://dominichopf.de/ Key Fingerprint: A7DF C4FC 07AE 4DDC 5CA0 BD93 AAB0 6019 CA7D 868D signature.asc Description: Dies ist ein digital signierter Nachrichtenteil ___ Geany-devel mailing list Geany-devel@uvena.de http://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] Shift-10 on editor tab
2010/3/3 Can Koy : > Hi, > Shift-F10 in an editor tab pops up a nice list of open documents. > I'm proposing to change this shortcut to Shift-MenuKey. I can add, instead of > replace, it if Shift-F10 is too important for you, but replacing is easy. > What do you think? Hi Can, I think Shift+F10 is something like a default behaviour which is written down in some guidline or anything like that. Also, many users may already know Shift+F10 as usual keybinding, so replacing it wouldn't be the best solution. So, adding Shift+MenuKey instead of replacing would be my choice. Regards, Dominic ___ Geany-devel mailing list Geany-devel@uvena.de http://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] [Patch] - Fix keyboard accelerators on Debug Messages window
Am Donnerstag, den 25.02.2010, 05:08 -0800 schrieb Can Koy:
> Apparently, messing with stock items was a bad idea. Please ignore the prev.
> patch, here's the new patch:
>
> Index: src/log.c
> ===
> --- src/log.c (revision 4704)
> +++ src/log.c (working copy)
> @@ -180,7 +180,7 @@
>
> dialog = gtk_dialog_new_with_buttons(_("Debug Messages"),
> GTK_WINDOW(main_widgets.window),
> GTK_DIALOG_DESTROY_WITH_PARENT,
> - GTK_STOCK_CLEAR, DIALOG_RESPONSE_CLEAR,
> + _("Cl_ear"), DIALOG_RESPONSE_CLEAR,
> GTK_STOCK_CLOSE, GTK_RESPONSE_CLOSE, NULL);
> vbox = ui_dialog_vbox_new(GTK_DIALOG(dialog));
> gtk_box_set_spacing(GTK_BOX(vbox), 6);
Applied, thanks!
Can, would it be possible to attach your patches as *.patch-file in
future contributions? - That would make it much easier to apply your
patches. :)
Regards,
Dominic
--
Dominic Hopf
http://dominichopf.de/
Key Fingerprint:
A7DF C4FC 07AE 4DDC 5CA0 BD93 AAB0 6019 CA7D 868D
signature.asc
Description: Dies ist ein digital signierter Nachrichtenteil
___
Geany-devel mailing list
Geany-devel@uvena.de
http://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] Race condition when saving geany.conf
Am Mittwoch, den 24.02.2010, 12:04 +0300 schrieb Eugene Arshinov: > Hi all. > > When several instances of Geany quit in the same time, there is a high > possibility of a conflict. I can reproduce it easily on my machine, > using either trunk or SM version. > > To reproduce: open three instances of geany, "geany", "geany -i" and > another "geany" (absence of file names implies -i automatically in > this case). It would be better to open three different files in > the instances, to distinguish them. Then logout or reboot without > quitting geany manually. On my machine, after I (in case of > trunk) or SM code (in case of SM) restart geany, the default session is > always cleared. Expected behaviour: the default session is managed by > the first of the three instances and contains the files, which > were opened in that instance, after restart. > > I can see two solutions for this problem. The first is an > additional POSIX process-shared semaphore / mutex for Windows to guard > geany.conf. This should eliminate the problem completely. AFAIK, there > are no wrappers for process synchronization primitives in GLib, so I'll > need to write a thin wrapper myself. > > The second option is to change the behaviour of "new instances". If > such an instance (#1) detects a "main instance" (#2) running, it should > not touch geany.conf. Actually, to deal with the described issue, it > is enough to implement this behaviour only when #1 tries to save > geany.conf while quitting. > > The second option is easier to write as it does not require > additional synchronization primitives and it's possible to reuse the > code of socket.c. Actually, I already have this option implemented, to > check whether it indeed solves the problem. But, you see, this > solution can't prevent the race condition completely, in distinction > from the first solution. Moreover, some of you may consider the second > solution "hackish", which is enough to decline it. > > So, the first solution is right, but the second is easy :-) What do you > think? There always are elegant solutions to solve a problem and maybe solutions which are not that elegant but would work too. If I understood you right, the first one would be the one more elegant? I'd always prefer an elegant solution over one which is not that elegant. :) Regards, Dominic -- Dominic Hopf http://dominichopf.de/ Key Fingerprint: A7DF C4FC 07AE 4DDC 5CA0 BD93 AAB0 6019 CA7D 868D signature.asc Description: Dies ist ein digital signierter Nachrichtenteil ___ Geany-devel mailing list Geany-devel@uvena.de http://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] Introduction - Can Koy
Am Donnerstag, den 25.02.2010, 03:25 -0800 schrieb Can Koy: > Hi, > > My name is Can Koy, and I live in Ankara, Turkey. > (for those confused, my name's pronounced like 'John'). > > My interest in Geany is purely selfish. I just wanted to have a good, robust, > fast, intuitive, versatile editor, without 1970's visuals(!), on Linux. So > far, Geany is the closest to match those and fulfill my needs (shell script, > config files, php, html, css, etc). > > I did a lot of C programming in the past on Win32, Un*x, MS-DOS. Now I intend > to apply those skills to fix/enhance Geany and, hopefully, eliminate some > frustrations I have while using it. > > Thanks, bye. Welcome to the Geany project then, Can. :) -- Dominic Hopf http://dominichopf.de/ Key Fingerprint: A7DF C4FC 07AE 4DDC 5CA0 BD93 AAB0 6019 CA7D 868D signature.asc Description: Dies ist ein digital signierter Nachrichtenteil ___ Geany-devel mailing list Geany-devel@uvena.de http://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] Doc errata?: Inserting Unicode characters.
Am Sonntag, den 21.02.2010, 14:09 -0800 schrieb Tony Rick: > On Sun, Feb 21, 2010 at 1:49 PM, Tony Rick wrote: > On Sun, Feb 21, 2010 at 1:29 PM, Lex Trotman > wrote: > > > Weird, never noticed that finishing the input > with Space works as well. > Anyway, the note about unbinding Ctrl-Shift-u > in the preferences was > added because in older versions we accidently > used Ctrl-Shift-u as > default for another keybinding. Maybe the note > could be changed to > reflect that. > However, I don't get it to insert a line break > even when using > Enter/Return to finish the Unicode input. > > > > Enrico, I think the problem is that the manual says > let go ctrl-shift before typing return, holding > ctrl-shift and typing return inserts the Unicode point > without the return but any character, including > return, typed after releasing the ctrl-shift inserts > the Unicode point and itself. I thought this was a > feature :-D > > Cheers > Lex > > > I realized about holding ctrl-shift for the Enter/Return, and > just figured that I mis-read the the manual (without actually > checking), but Lex beat me to the punch. I guess this is a doc > modification, too. I'll do it, unless somebody else beat me > to that, too. > > - tony > > > ...and here's the patch for the manual (against revision 4688). Applied, thanks! -- Dominic Hopf http://dominichopf.de/ Key Fingerprint: A7DF C4FC 07AE 4DDC 5CA0 BD93 AAB0 6019 CA7D 868D signature.asc Description: Dies ist ein digital signierter Nachrichtenteil ___ Geany-devel mailing list Geany-devel@uvena.de http://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] Project-specific long line marker position
Am Sonntag, den 21.02.2010, 18:34 +0300 schrieb Eugene Arshinov: > [1] Preferences Dialog: <http://xmages.net/upload/839ca662.png> > [2] Project Properties: <http://xmages.net/upload/602c3e80.png> The screenshots look very cool! -- Dominic Hopf http://dominichopf.de/ Key Fingerprint: A7DF C4FC 07AE 4DDC 5CA0 BD93 AAB0 6019 CA7D 868D signature.asc Description: Dies ist ein digital signierter Nachrichtenteil ___ Geany-devel mailing list Geany-devel@uvena.de http://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] Javascript keyword list
Am Dienstag, den 16.02.2010, 13:49 +0100 schrieb Jonas H.: > Hi, > > you have a lot of crap in the javascript keyword list. I attached a > correct, up-to-date list. (At least I think it's correct and > up-to-date). Here it comes: > > [keywords] > # all items must be in one line > primary=break case catch const continue delete else eval false finally > for function if in try instanceof isFinite isNaN NaN new null return > switch this throw true typeof undefined var while with default let > secondary=Object Function Array prototype Hi Jonas, I applied your changes in SVN revision 4677. Thank you very much for pointing this out! Regards, Dominic -- Dominic Hopf http://dominichopf.de/ Key Fingerprint: A7DF C4FC 07AE 4DDC 5CA0 BD93 AAB0 6019 CA7D 868D signature.asc Description: Dies ist ein digital signierter Nachrichtenteil ___ Geany-devel mailing list Geany-devel@uvena.de http://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] old custom filetypes branch - Re: Separate color schemes and filetype definitions
Am Mittwoch, den 17.02.2010, 13:01 + schrieb Nick Treleaven: > On Tue, 16 Feb 2010 21:28:24 +0100 > Dominic Hopf wrote: > > > The filetype definition system is under rework at the present. I think > > some of the problems you mentioned may already be solved there. It is > > developed in a separate branch, but you can follow the development if > > you like. Check out > > > > https://geany.svn.sourceforge.net/svnroot/geany/branches/custom-filetypes > > This is an old branch I forgot to remove. It's been merged to trunk. > (Under Document->Set Filetype you should have a 'Custom Filetypes' menu > with an item for Genie). It actually is there, yes. Sorry for the confusion. :) -- Dominic Hopf http://dominichopf.de/ Key Fingerprint: A7DF C4FC 07AE 4DDC 5CA0 BD93 AAB0 6019 CA7D 868D signature.asc Description: Dies ist ein digital signierter Nachrichtenteil ___ Geany-devel mailing list Geany-devel@uvena.de http://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] Doc patch: Tools->Reload Configuration effects
Am Freitag, den 19.02.2010, 22:23 -0800 schrieb Tony Rick: > As far as I can tell, Tools->Reload Configuration loads all > configuration and template files, including geany.conf. I have > attached a patch for your consideration, conf_reload.patch, that adds > comments to that effect everywhere that they apply. In some cases I > also edited the surrounding text in an attempt to reduce > repetition/confusion. Sorry for the typo in my commit message. :) -- Dominic Hopf http://dominichopf.de/ Key Fingerprint: A7DF C4FC 07AE 4DDC 5CA0 BD93 AAB0 6019 CA7D 868D signature.asc Description: Dies ist ein digital signierter Nachrichtenteil ___ Geany-devel mailing list Geany-devel@uvena.de http://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] Doc patch: Tools->Reload Configuration effects
Am Freitag, den 19.02.2010, 22:23 -0800 schrieb Tony Rick: > As far as I can tell, Tools->Reload Configuration loads all > configuration and template files, including geany.conf. I have > attached a patch for your consideration, conf_reload.patch, that adds > comments to that effect everywhere that they apply. In some cases I > also edited the surrounding text in an attempt to reduce > repetition/confusion. > > - tony Patch applied in SVN revision 4676. Thanks! -- Dominic Hopf http://dominichopf.de/ Key Fingerprint: A7DF C4FC 07AE 4DDC 5CA0 BD93 AAB0 6019 CA7D 868D signature.asc Description: Dies ist ein digital signierter Nachrichtenteil ___ Geany-devel mailing list Geany-devel@uvena.de http://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] geany.txt - Re: [ANNOUNCEMENT] website rework
Am Mittwoch, den 17.02.2010, 13:24 + schrieb Nick Treleaven: > On Tue, 16 Feb 2010 15:22:06 +1100 > Lex Trotman wrote: > > > The only other comment is that if someone is only doing documentation, they > > really only need to check out trunk/doc/geany.txt not the whole SVN. > > Yes, but then they need to know how to generate the HTML to at least > check the source is not malformed. You can't type 'make doc' without > the full build system. I've added an additional note about that, thanks very much for pointing this out! Regards, Dominic -- Dominic Hopf http://dominichopf.de/ Key Fingerprint: A7DF C4FC 07AE 4DDC 5CA0 BD93 AAB0 6019 CA7D 868D signature.asc Description: Dies ist ein digital signierter Nachrichtenteil ___ Geany-devel mailing list Geany-devel@uvena.de http://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] Separate color schemes and filetype definitions
Am Dienstag, den 16.02.2010, 14:03 +0100 schrieb Jonas H.: > My suggestion is: Separate filetype definitions and color schemes. For > example, think of two directories, "colorschemes" and "filedefs". A > filedef file contains stuff like a keyword list and so on. A color > scheme file contains nothing more but kinda > keyword-type-color-assignment, such as > >primary = #somecolor > > Furthermore I would implement something like inheritance, escpecially > for filedefs. Let me explain what I mean by 'inheritance' in that case: > > You have default filedefs in /usr/share/geany/fildefs (or whatever). If > a custom filedef is given in .config/geany/filedefs (or whatever), all > 'keys' given in that custom file will be overriden. Advantage of this > is: The custom files don't have to be a 1:1 copy, but only some kind of > 'override-file'. > > Advantage of this is: You can have custom settings for example for > compile commands, but still can go with the current up-to-date keyword > list (delivered with Geany). > > What do you think? Hi Jonas, welcome to the Geany development list. :) I like your suggestions, but I'm actually not sure if they may already are implemented in SVN - maybe in a bit different way. The filetype definition system is under rework at the present. I think some of the problems you mentioned may already be solved there. It is developed in a separate branch, but you can follow the development if you like. Check out https://geany.svn.sourceforge.net/svnroot/geany/branches/custom-filetypes for that. Regards, Dominic -- Dominic Hopf http://dominichopf.de/ Key Fingerprint: A7DF C4FC 07AE 4DDC 5CA0 BD93 AAB0 6019 CA7D 868D signature.asc Description: Dies ist ein digital signierter Nachrichtenteil ___ Geany-devel mailing list Geany-devel@uvena.de http://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] [ANNOUNCEMENT] website rework
Hi Lex, Am Dienstag, den 16.02.2010, 15:22 +1100 schrieb Lex Trotman: > Hi Dominic, > > Nice, I like the clean background, but then I run my monitors at > medium brightness because I get a lot of white backgrounds, eg PDFs > > Attached are patches against the HTML. They only change some minor > English and punctuation. Thanks very much for the patches. I applied them immediately. :) > The only other comment is that if someone is only doing documentation, > they really only need to check out trunk/doc/geany.txt not the whole > SVN. I added a hint about that, you maybe want to have another look there. :) Regards, Dominic -- Dominic Hopf http://dominichopf.de/ Key Fingerprint: A7DF C4FC 07AE 4DDC 5CA0 BD93 AAB0 6019 CA7D 868D signature.asc Description: Dies ist ein digital signierter Nachrichtenteil ___ Geany-devel mailing list Geany-devel@uvena.de http://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
[Geany-devel] [ANNOUNCEMENT] website rework
Hello together, I just wanted to let you know that I gave some love to the geany.org website today (since it was Valentines day yesterday ;) ). No big thing, don't expect a full re-design or anything. What you will see is: * There is a new page "Reviews" in the "Geany" section, where to write about any website which provides Reviews about Geany. If you know any website, blog or online magazine which wrote about Geany, please let me know so I can add it there. * There is a new section called "Contribute", including four new pages: Developers, Translators, Documentation and Support. Please pay attention to those and let me know if you agree or dis-agree with the things I wrote there, if you're missing something or if you found any issue to fix. Feedback is highly appreciated. * Any text on geany.org got a small rework, in special I changed some wording issues and added links to other pages within the texts so handling for users and new visitors should be easier. I also removed any open-in-new-window-or-tab links since it should be the users decision if he wants a link to open in a new browser tab or window or anything else. Another thing I did here was to make consistent use of header levels - that means, changed some headers from h3 to h2 and so on... * I gave some love to the css file and redesigned the headers, added some letter-spacing, increased the above and below the header and changed the color of the headers to gray. - Let me know if you like it or not What still has to be done is updating the screenshot gallery as I promised on IRC today. If you like to make some screenshots of your Geany in action, feel free to send them to me but consider to not shoot any content which may be sensible. Best Regards, Dominic -- Dominic Hopf http://dominichopf.de/ Key Fingerprint: A7DF C4FC 07AE 4DDC 5CA0 BD93 AAB0 6019 CA7D 868D signature.asc Description: Dies ist ein digital signierter Nachrichtenteil ___ Geany-devel mailing list Geany-devel@uvena.de http://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] Command-line option to open a project (was: Questions about Geany project support)
Hey Eugene, Am Montag, den 15.02.2010, 14:12 +0300 schrieb Eugene Arshinov: > Hi all. Here is the last question. > > Preface. > Currently if the first filename passed via command-line has ".geany" > extension, it's opened as a project. If I implement project support > in SM using this behaviour, there will be a little trouble. > > The trouble. > Suppose a user has neither default session not a project opened > (example: "geany -s"), and he opens a project file to edit it manually. > Then if he logs out without closing Geany, my SM code has to store > opened files in restart command like "geany -s edited_proj.geany". You > see what happens after that when Geany is restarted. > > A solution. > Provide a separate command-line option to open a project (e.g., > "--project" or "-r" as "-p" is reserved for "--no-plugins"). This > behaviour is more convenient and it eliminates the problem completely. > > Absence of compatibility (1). > BUT current behaviour is rather old and users may be familiar with it. > Maybe(?) it is acceptable to drop that behaviour completely and tell all > users about it (is there a way to do it? I believe that most of users > are not subscribed to Geany mailing list). If it isn't acceptable, see > below. I think it would be acceptable, even if compatibility is nicer. We have mailing lists, IRC channel and release notes where users can hear about any change. If there would be still a user who gets confused, he should subscribe to the mailing list and ask or at least file a bug at the sf tracker and hear about the change that way. I think that would be okay. > Making it compatible (2). > Geany instance has some means to know whether it's run by a user or > being restarted (via hidden command-line option I introduced to support > XSMP). If an instance if being restarted, it is completely safe to > disable the old behaviour and enable the new one. That solves the > problem. I tend to drop the old behaviour as written above. But let's wait for other opinions. Maybe the compatibility is the better solution. > Removing the old behaviour (3). > From my point of view, it is not comfortable to maintain two variations > of handling command-line options (though the difference between them is > little). Maybe(?) it is acceptable to keep the old behaviour in the > next version (say, 0.19), but issue a warning to stderr when the old > behaviour is used, and remove the old behaviour some time after that > (say, in 0.20). That's the way I'd also prefer about compatibility, since it's just a "smoother" (1). :) Regs, Dominic -- Dominic Hopf http://dominichopf.de/ Key Fingerprint: A7DF C4FC 07AE 4DDC 5CA0 BD93 AAB0 6019 CA7D 868D signature.asc Description: Dies ist ein digital signierter Nachrichtenteil ___ Geany-devel mailing list Geany-devel@uvena.de http://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] Build system branch 2.0
Am Samstag, den 13.02.2010, 16:58 +0100 schrieb Enrico Tröger: > On Sat, 6 Feb 2010 21:21:03 +1100, Lex wrote: > > Heya guys, > > since we have quite different ideas of the future of the whole build > systems features and in particular about its configuration using GUI > dialogs, I got a weird idea: > > Why not moving the build system code into a plugin? > > This isn't completely new, I think to remember we discussed this before > Lex' first rewrite of the build system and decided to not do this to > keep it in the core and so always available. > > Though having the build system as a plugin has some advantages, IMO. > > First, Lex could realise it as he wants, as complex and flexible as > necessary giving users all the powers they want to and don't limit them > with any hardcoded defaults (I completely understand this wish). > > And alternatively, we could implement a very basic, limited and easy to > use(KISS) build system alternatively, similar to the old one(as in 0.18 > and before) alternatively to the advanced one. > > Then users can choose which build system plugin they want to use and so > have even more flexibility. > > > This would probably make things a bit harder and would require some > additions to the plugin API, especially to get project support properly > involved but I think it might be worth in the long term. Basic functionality for building, compiling and running programs (yes, as in 0.18 and before) should definitely keep included in Geanys core. Functionality which extends (or even might replaces) this - as Lex's effort does - could be implemented as a plugin, yes. I personally prefer any KISS solution over a solution which just provides (maybe too much) features. The hit-you-in-the-face-factor, you know? ;) From the user point of view the dialog for setting includes and arguments in current SVN trunk is okay so far concerning the hyitf-factor. It maybe could be optimized in other apsects, in special I am missing tooltips which explain the fields as in any other place in Geany. The usage of the GtkExpander in the right place could even reduce the hyitf-factor a bit. ;) Regards, Dominic -- Dominic Hopf http://dominichopf.de/ Key Fingerprint: A7DF C4FC 07AE 4DDC 5CA0 BD93 AAB0 6019 CA7D 868D signature.asc Description: Dies ist ein digital signierter Nachrichtenteil ___ Geany-devel mailing list Geany-devel@uvena.de http://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] Project-specific long line marker position
Am Donnerstag, den 11.02.2010, 22:58 +0300 schrieb Eugene Arshinov: > Hi all. > > I usually limit line length by 80 in my own projects, but in Geany 100 > symbols is recommended. If the long line marker position preference was > project-specific, I would not need to change it in the Preferences > dialog every time I switch between Geany sources and one of my projects. > > If making this preference project-specific makes sense for you, I can > spend some time to implement it. Otherwise, I will just ignore the > issue (I don't consider it important). > > Best regards, > Eugene. Hi Eugene, I really think this feature would make sense for me too, so I'd appreciate this too, but I also don't consider it as that important, it's more a nice-to-have than a must-have for me. :) Regards, Dominic -- Dominic Hopf http://dominichopf.de/ Key Fingerprint: A7DF C4FC 07AE 4DDC 5CA0 BD93 AAB0 6019 CA7D 868D signature.asc Description: Dies ist ein digital signierter Nachrichtenteil ___ Geany-devel mailing list Geany-devel@uvena.de http://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] Build system branch 2.0
Am Samstag, den 06.02.2010, 21:21 +1100 schrieb Lex Trotman: > Hi All, > > I have created a branch for further development of the build system called > bs2. > > I have added the current state of the design spec to the doc directory > and a temporary Python prototype implementation of the configure > dialog in scripts (since I know how much you all hate reading GUI > descriptions). It is intended to delete this before merge but it will > be useful to get ideas on making it usable, for example which fields > should be visible normally and which only in advanced mode. > > @Nick as the padding guru you might have some suggestions, in my > opinion applying padding to rows containing buttons or combo boxes > makes a disproportionate increase in size, so for now I've taken it > off, see what you think. > > Running the script (python build_dialog_prototype.py) produces a > window with two buttons, one produces the dialog as it will be when no > project is open and one as it will be when a project is open. Clearly > the dialog has no code or data behind it, but the "advanced" and "show > all" buttons work. Apply, cancel and ok all close the dialog. > > Please be warned, if you havn't read the spec (which is the only > documentation until the manual is updated) that this looks complex > when you first see it in advanced mode. But the dialog does no more > than bring together settings that already exist in various hidden > places in Geany. > > Cheers > Lex Wouldn't it have had to be easier to design that with glade instead of writing python scripts? - Or alternative, a pen and paper? ;) When seeing this from a user point of view there is very much information to enter. A bit "overload" on the screen - in special the advanced mode. Yes, you warned me. ;) As you said, this is a prototype which maybe needs more work. - Also from the user point of view and in GUI design. Just a suggestion: You could work with the GUI element from GTK which allows to extend the dialog via clicking on the arrow (as in the Find or Replace dialog in Geany) :) Regards, Dominic -- Dominic Hopf http://dominichopf.de/ Key Fingerprint: A7DF C4FC 07AE 4DDC 5CA0 BD93 AAB0 6019 CA7D 868D signature.asc Description: Dies ist ein digital signierter Nachrichtenteil ___ Geany-devel mailing list Geany-devel@uvena.de http://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] Safe file saving
Am Freitag, den 05.02.2010, 12:14 +0300 schrieb Алексей Антипов: > > > 2. (Possibly, but not necessarily) make this option > > > (use_save_file_saving) accessible through the GUI > > > > Really? > > I think this would cause mainly just confusion. It just isn't that easy > > to explain what's the story behind this option. No idea. > > > Alright; IMHO, all the configuration options should be documented somewhere > (I've found this one only while looking through the code), but it's not a > question of that issue. I'd suggest to make this a hidden setting. Those already are documented: http://geany.org/manual/#hidden-preferences General documentation for the preferences dialog also is available: http://geany.org/manual/#id77 Best Regards, Dominic -- Dominic Hopf http://dominichopf.de/ Key Fingerprint: A7DF C4FC 07AE 4DDC 5CA0 BD93 AAB0 6019 CA7D 868D signature.asc Description: Dies ist ein digital signierter Nachrichtenteil ___ Geany-devel mailing list Geany-devel@uvena.de http://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] developers help
Am Freitag, den 29.01.2010, 20:05 +0600 schrieb Alexander Kuleshov: > Hello. My name is Alexander. I am a programmer P / C + +, python, etc. > Would like to help the project. What should I do? Can I make a > function from the WishList? What do I do? > Thanks Hi Alexander, first of all: Welcome to the Geany Project. There are a few things you should have a look (if you didn't yet). There is a bug tracker at [1] and a feature tracker at [2] which maybe contain bug reports or even feature requests which may already have a patch attached. To avoid redundant efforts, it's always a good idea to have a look there first, if there already is anything concerning the topic. There are also mailing lists archives where you can find, if topics maybe already were discussed. You can find them at [3] and [4]. I assume, for current discussions, you already subscribed to both, users and developers list? :) Before beginning with hacking, you should have a look on the HACKING file at [5] - if you haven't yet. Some points where you can begin: * fix bugs found in the bug trackers, send a patch to this mailing-list (geany-devel@uvena.de) * add new features you found in the tracker, but first decide, if it should be a core feature or better implemented in a plugin. If you're not sure, you can discuss this on this mailing list. * write new plugins from the wishlist you can find at [6], note that this is a plugin wishlist, which shouldn't contain any wishes for core features. If you're going to write a plugin it would be cool if you write your README file in restructuredText. I'm currently working on a new plugins.geany.org (a preview can already been seen at plugins2.geany.org) and I'm in excessive use of restructuredText to update the site automagically. I hope this informations are helpful for you so far. If you like to have SVN access for Geany or Geany Plugins, just tell us, one of the sf.net admins for these projects can setup the access for you then. Feel free to ask here if you have any questions. :) Best Regards, Dominic [1] http://sourceforge.net/tracker/?group_id=153444&atid=787791 [2] http://sourceforge.net/tracker/?group_id=153444&atid=787794 [3] http://news.gmane.org/gmane.editors.geany.devel [4] http://news.gmane.org/gmane.editors.geany.general [5] http://geany.svn.sourceforge.net/viewvc/geany/trunk/HACKING?view=log [6] http://www.geany.org/Support/PluginWishlist -- Dominic Hopf http://dominichopf.de/ Key Fingerprint: A7DF C4FC 07AE 4DDC 5CA0 BD93 AAB0 6019 CA7D 868D signature.asc Description: Dies ist ein digital signierter Nachrichtenteil ___ Geany-devel mailing list Geany-devel@uvena.de http://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] Moving XML/HTML specific stuff into plugin
Am Sonntag, den 17.01.2010, 16:48 +0100 schrieb Enrico Tröger: > On Sat, 16 Jan 2010 20:52:04 +0100, Frank wrote: > > >Hi > > > >During my work on moving some LaTeX specific functions from Geany core > >to geanyLaTeX plugin I recognized some code which is pretty much > >HTML/XML specific and might would make sense to move also into a > >plugin. On first step I was thinking about moving auto_table() out of > >editor.c, but there are a couple of more things like the automatic > >closing of XML tags which might would make sense to move into a > >separate plugin. > > > >Lets give you a short list of advantages/disadvantages I can imagine > >off doing such a step: > > > >Advantages: > >+ Geany's core is keeping small and as we don't need to care about too > >much filetype specific stuff > >+ Save some CPU cycles on every change on editor widget for users which > >don't use XML/HTML as the check for this types will not be needed > >anymore > >+ More flexibility in upgrading the fileype specific functions when > >realized as a plugin > >* Possible more configuration possibilities for user without bloating > >Geany's preferences dialogues itself for non-XML/HTML users > > > >Disadvantages > >- With a new plugin the user needs to know about and needs to activate > >it > >- User might think Geany is not support HTML properly as he wasn't > >aware of n-1 > >- Additional overhead on > > * coding > > * running the plugin through plugin API > > > >Please let me know what you think about. > > I'm not sure whether we should do this. > Basically you are completely right about moving filetype specific code > from the core into a plugin. But we also have little specifics for > other filetypes, e.g. auto indenting in Python after typing a colon. > These little things don't match the requirement to be moved into a > plugin, IMO. Though in case of the HTML/XML features, there is a lot > more stuff which we do so we are talking about a good bunch of code not > only a few lines. > Still I think it could become a bit cumbersome for users to enable a > specific plugin to have the functionality they were used to have in > Geany for ages. > And then there is the fact the code in question in used for HTML *and* > XML which are two separate filetypes. How should a user expect that he > have to enable a HTML plugin to get tag auto closing in XML files? > > After all, I rather think we should keep it in the core even though > it's mainly for the better user experience. Exactly my point of view. I fully agree to Enrico here. Regs, Dominic -- Dominic Hopf http://dominichopf.de/ Key Fingerprint: A7DF C4FC 07AE 4DDC 5CA0 BD93 AAB0 6019 CA7D 868D signature.asc Description: Dies ist ein digital signierter Nachrichtenteil ___ Geany-devel mailing list Geany-devel@uvena.de http://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] Nightly build changes
Am Sonntag, den 17.01.2010, 16:04 +0100 schrieb Enrico Tröger: > 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 :). Your welcome. ;) > [1] > http://geany.svn.sf.net/viewvc/geany/trunk/scripts/plugin_test.c?revision=4526&view=markup > > Regards, > Enrico > > P.S.: sorry for the long and boring story but maybe someone finds it as > interesting as me :). At least me. -- Dominic Hopf http://dominichopf.de/ Key Fingerprint: A7DF C4FC 07AE 4DDC 5CA0 BD93 AAB0 6019 CA7D 868D signature.asc Description: Dies ist ein digital signierter Nachrichtenteil ___ Geany-devel mailing list Geany-devel@uvena.de http://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] Questions about Geany project support
Am Sonntag, den 10.01.2010, 18:38 +0300 schrieb Eugene Arshinov:
> Hi all.
>
> Preface
> ---
>
> Recently I realized that I completely forgot to integrate project
> support into my XSMP support (which would reside in "sm" branch after
> some of my patches are committed). Currently my code stores open
> files, but it does not remember the project, if any was opened when
> Geany terminated.
>
> I was looking through the code to understand how the integration could
> be implemented and testing how Geany behaves on opening and closing
> projects. I discovered some issues, and there are also some questions
> I'd like to ask. After all problems are solved and questions are answered,
> I'll prepare some more patches for "sm" branch.
>
> Question #1
> ---
>
> `load_startup_files' function within main.c (formatting is wrong):
>
> /* when we want a new instance, we still load project session files
> unless -s was passed */
> if (!cl_options.load_session ||
>(!load_project_from_cl && cl_options.new_instance)) return;
>
> Specifying "-s" while opening a projects causes Geany to open a blank
> document.
>
> First, when geany instance is closed, the project is overwritten.
> Instead of the files which were previously there, there would be no
> files in the project. Is it a desired behaviour? Is it a desired way to
> clear a project?
>
> Second, it is not intuitive. From my point of view, "-s" is
> there to not load the default session. When user tries to open a
> project and specify "-s", he should wish to open the project's files
> and not load the default session. Currently opening a project forbids
> loading the default session, so "-s" is not necessary. But I think the
> behaviour I described ("-s" is ignored) is more logical than opening a
> blank document instead of project's files.
I agree to this one. I'd also expect the project files to be opened.
Regards,
Dominic
--
Dominic Hopf
http://dominichopf.de/
Key Fingerprint:
A7DF C4FC 07AE 4DDC 5CA0 BD93 AAB0 6019 CA7D 868D
signature.asc
Description: Dies ist ein digital signierter Nachrichtenteil
___
Geany-devel mailing list
Geany-devel@uvena.de
http://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] Geany-devel Digest, Vol 21, Issue 14
Am Dienstag, den 22.12.2009, 16:10 +0100 schrieb Lionel Fuentes: > 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 "-". Fixed for now. This is still a point where I have to do manual efforts, I didn't found a way yet to automate this. ;) Reviewing the site and claiming mistakes is a good compromise until I finished the automation scripts [1] :) [1] I was talking with Enrico some days ago about automating the process a bit more as it is at the present since most documents already were generated by rst2html and cleaned up a bit by using tidy. Ideal goal of the automation scripts is, that you just will have to update your README and anything else is done by the server. I guess that won't be an easy hack, but well, let's see if I get this working. ;) Regards, Dominic -- Dominic Hopf http://dominichopf.de/ Key Fingerprint: A7DF C4FC 07AE 4DDC 5CA0 BD93 AAB0 6019 CA7D 868D signature.asc Description: Dies ist ein digital signierter Nachrichtenteil ___ Geany-devel mailing list Geany-devel@uvena.de http://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] Changing from scintilla to gtksourceview or scintilla over gtksourceview
Am Mittwoch, den 30.12.2009, 00:26 +0100 schrieb Enrico Tröger: > On Tue, 29 Dec 2009 21:12:36 +0100, Thomas wrote: > > >Am 29.12.2009 19:55, schrieb Enrico Tröger: > >> An interesting question could be which engine is faster but this is > >> probably hard to test and maybe not even worth if the difference is > >> quite small or not even noticeable. > > > > From my POV, scintilla is pretty slow. Especially on windows where > >scrolling is painfully slow, but also for opening the > > This isn't strictly Scintilla's fault. It's rather because of the fact > that we use the GTK port of Scintilla on Windows while Scintilla has > its own Windows port which runs way faster. But using it isn't that > easy as everything around is still GTK. But this is something we maybe > could improve. > > > >auto-completition list (although I remember it was way faster some > >month ago, so it could be my system(s)). I don't know whether > > The question is whether really the plain displaying(i.e. drawing it on > the screen) of the list is slow or whether generating the contents of > the list is slow. The drawing is Scintilla's part, filling values into > the list is Geany's part which could also be slow. > > > Regards, > Enrico For those guys having performance problems on Windows with Geany, I would recommend to have a look on Programmers Notepad: www.pnotepad.org, it uses - other than Geany - the Windows port of Scintilla (AFAIK). This also would have the effect, that it could be found out if there is a generic problem or a problem related to the GTK port of Scintilla (or maybe even Geany). Hope that maybe helps out the Windows-using guys until the Windows-Port of Geany got improved ;) Btw: I personally did not have any problems with Geany on Windows yet, just one time Geany used 100% CPU, in month of using Geany on Windows at work. And I'm using the nightly builds. :) Regards, Dominic -- Dominic Hopf http://dominichopf.de/ Key Fingerprint: A7DF C4FC 07AE 4DDC 5CA0 BD93 AAB0 6019 CA7D 868D signature.asc Description: Dies ist ein digital signierter Nachrichtenteil ___ Geany-devel mailing list Geany-devel@uvena.de http://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
[Geany-devel] [Geany Plugins] New website in work
Hi guys, as promised in a mail few weeks ago I'm working on a new website for plugins.geany.org. A first impression is already available at [1]. Any feedback is appreciated. Note that there is still content missing about some plugins since I didn't found time yet to work on every plugin page. Just for your information, since I will maintain the site in future: I developed a small process (mainly for me myself) to make sure the maintenance of the site will stay as easy as it is at the present. There are some configuration files available for rst2html and HTML Tidy at [2], [3] and [4]. A small description of the idea behind these files is available at [5]. This process implicates, that any information provided on [1] will be in sync with your README files. I would just add navigation features and such things to make it easy for a visitor to navigate through the site and maybe also fix some typos and other syntax concerned issues but not change any content related to your plugins. Actually, this already happened for some plugins as you can see at [1]. In cases I am doing changes (like fixing typos) to README files, I'll write a mail including a patch to the affected plugin developer. Generating the content for the website from every README file means also, if your README files are not up to date, the website also isn't. For this reason I'd like to remember you to check your README files time after time and see if any changes are necessary. Please let me know what you're thinking of this prove of concept (generating content from your README files) and maybe if you think there are better ways to implement the site, I'd be happy about any feedback. :) I'm going for winter vacancies tomorrow and will be back in the beginning of January, so most likely the site won't go live anymore this year. Wish you all a merry x-mas and a happy new year! Best Regards, Dominic [1] http://plugins2.geany.org/index.php [2] http://plugins2.geany.org/content/rst2html_config.conf [3] http://plugins2.geany.org/content/rst2html_template.txt [4] http://plugins2.geany.org/content/tidy.conf [5] http://plugins2.geany.org/index.php?site=README -- Dominic Hopf http://dominichopf.de/ Key Fingerprint: A7DF C4FC 07AE 4DDC 5CA0 BD93 AAB0 6019 CA7D 868D signature.asc Description: Dies ist ein digital signierter Nachrichtenteil ___ Geany-devel mailing list Geany-devel@uvena.de http://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
