Devel November 2009

devel@lists.geany.org

13 participants
17 discussions

Geany Plugins 0.18 released!
by Chow Loong Jin 15 Nov '09

15 Nov '09

Hi all, We're happy to announce a new release of Geany Plugins, 0.18. Below is a shortlog of all the changes since 0.17.1:- eht16 (16): Attempt to fix crashes when quitting Geany from the system tray icon. ChangeLog updated :-) Fix wrong indentation level Avoid using GHashTable functions from newer GLib versions to fix compilation with GLib 2.8. Fix version number We need the dot for proper building (e.g. on Windows). Merge changes from trunk Merge changes from trunk: Allow setting a custom dictionary directory without reloading the plugin. Add an option to the preference dialog to select a custom directory to look for additional dictionary files. Minor fixes. Remove unused code. Use single header includes. Update NEWS Fix wrong cast for Geany 0.18 Add readme file for Windows mentioning the included binaries Update outdated information Update outdated information Install README.windows Beautify the filename Update for 0.18, install plugin dependencies as well frlan (13): Backport bugfix for geanyLaTeX toolbar to 0.17.1 tree Update some of the documentation files to avoid empty files. Closes #2823235 Backport some of updated translation to 0.17.1 branch Create branch for 0.18 tree Update of version strings and set minimum depedency for Geany to 0.18 Update of documentation Update missed css file Update geanyvc to current devel version for 0.18 release Update NEWS file a bit GeanyVC: Fix a tooltip Set binary flag for geanyLaTeX's documentation PDF GeanyLaTeX: Also replace capital German Umlauts. Update/Backport of translations for 0.18 release hyperair (14): Correct typo: COMMON_LIBS => COMMONLIBS Move ttyhelper to $libexecdir/geany-plugins/geanygdb Tag geany-plugins-0.17.1 release Bump version in configure.ac Bump version in configure.ac Bump versions in wscript and .nsi Create tag geany-plugins-0.17.1 Port build system updates from trunk Turn on automake silent rules if supported Correct typo geadydoc => geanydoc Include waf files into the tarball Add README for autotools Correct typo and spelling errors in README Add missing files to POTFILES.in ntrel (4): Create 0.17.1 bugfix branch copied from the 0.17 release. Fixes from trunk. Add NEWS from trunk. Minor reformatting. yurand (2): Added geanyprj and geanydoc plugins Don't use gettext for empty string -- Kind regards, Chow Loong Jin

5 15

Trying to make a Guile Scheme lexer
by Roberto Rosetti 15 Nov '09

15 Nov '09

Hi all, I'm trying to hack geany (0.18, for the moment) with a custom LexScheme.cxx scintilla lexer, build specifically for GNU Guile Scheme. I'm in trouble at the moment for a curious seg-fault I get loading an *.scm file I'm wondering how to insert some debugging code in the lexer module, where as the good old fprintf(stderr, ..) dont work at all. Can't include the geany_debug() function in the lexer module, right? I've used the geany hacking documentation, quite sure to have done all the necessary modifications in the various geany source file and configuration files. Any suggestion will be appreciated. :) (Please help!) -- -------------------------------------- Roberto Rosetti OpenPGP Public key: 30575161

5 7

[PATCH] [geany-plugins] [shiftcolumn] Use geanyplugin.h
by Eugene Arshinov 12 Nov '09

12 Nov '09

Hi all. I've just could not install shiftcolumn plugin from trunk on a clean system. In shiftcolumn.c sciwrappers.h is included, which is not installed since Geany r4366. The attached patch replaces includes in shiftcolumn.c with the single include file geanyplugin.h. After this change geany-plugins compiled successfully. The patch is against the latest trunk (that is, r1053). Best regards, Eugene.

2 5

Re: [Geany-devel] Manipulating build system from plugin
by Lex Trotman 07 Nov '09

07 Nov '09

Hi Frank, Yes, I think the build system can do what you want. With the new build system project files can contain filetype dependent commands that are defined only when the project is open. So: 1. the collection of latex files making the document should have a project file associated with them (maybe in the same directory as main.tex) 2. An extra filetype dependent command is defined in the project file that compiles main.tex (remember that by default you have 3 filetype dependent commands and can increase it if needed) 3. that command can be named something like "Compile Book" Then when you open the project you will get this extra command. The problem at the moment is that there is no GUI to edit this, (see the long discussion with Enrico in another thread re the configuration GUI). I am re-working the GUI at the moment but some of that "life" stuff that is causing Enrico so many problems has got in my way too :-). I hope to be able to do some work on it this weekend. In the interim you can hand edit the project file: add a [build-menu] section (or use the existing one if its already there) add a line (or add LaTeX to the existing line if its present): filetypes=LaTeX; add: LaTeXFT_02_LB=Compile Book LaTeXFT_02_CM=pdflatex main.tex LaTeXFT_02_WD= For the moment I recommend not accessing the build system from a plugin since its plugin API is likely to change, (see discussions with Nick). Any problems let me know as I suspect this has not been used anywhere other than my testing, so far. Cheers Lex 2009/11/7 <frank(a)frank.uvena.de>: > Hi Lex, > > I'm in discussion inside a feature request and I'm wondering whether you > see any chance doing this on Geany's current build system: > https://sourceforge.net/tracker/index.php?func=detail&aid=2893464&group_id=… > > Goal would be to react on some open tex file and set the build command > properly. Let's make an example: > chapter1.tex is part of a book which contains of many files, where the > main file is main.tex. Now if you have chapter1.tex open and push compile, > it might won't compile as the header might is missing. On emacs and vi and > ... you can define for this some local variable which is setting the master > file which is compiled instead. So something like %master: main.tex will > case the build command to run pdflatex main.tex whenever called from > chapter.tex. > > From best knowledge, I don't see any way to build this in a clear way. But > maybe I'm missing something. So I'm asking you ;) > > Cheers, > Frank >

1 0

Color schemes menu - Re: SF.net SVN: geany:[4395] trunk
by Nick Treleaven 04 Nov '09

04 Nov '09

Hi, On Wed, 04 Nov 2009 12:36:56 +0000 ntrel(a)users.sourceforge.net wrote: > Revision: 4395 > http://geany.svn.sourceforge.net/geany/?rev=4395&view=rev > Author: ntrel > Date: 2009-11-04 12:36:56 +0000 (Wed, 04 Nov 2009) > > Log Message: > ----------- > Add 'View->Editor->Color Schemes' menu, for now only shown if color > scheme files exist in a colorschemes config directory. Color scheme > files must end in ".conf" and currently only the [named_styles] > section is read. Some info on this: Basically ATM only named styles are allowed in color schemes, and only some filetypes support named styles - C-like filetypes. See attached for two (incomplete) test color scheme files to put in ~/.config/geany/colorschemes/. Test using C-like filetype documents or the None filetype. Regards, Nick

1 0

Re: [Geany-devel] SF.net SVN: geany:[4367] trunk
by Lex Trotman 04 Nov '09

04 Nov '09

Hi Nick, The documented functions in build.h were intended to be added to the API after discussions with Enrico in the past. Not sure why they weren't. What needs to be done to do that? Cheers Lex 2009/10/27 <ntrel(a)users.sourceforge.net>: > Revision: 4367 > http://geany.svn.sourceforge.net/geany/?rev=4367&view=rev > Author: ntrel > Date: 2009-10-26 14:59:47 +0000 (Mon, 26 Oct 2009) > > Log Message: > ----------- > Move function doc-comments to build.c so they stay in sync. Note: > these functions are still not in the API. > > Modified Paths: > -------------- > trunk/ChangeLog > trunk/src/build.c > trunk/src/build.h > > Modified: trunk/ChangeLog > =================================================================== > --- trunk/ChangeLog 2009-10-26 13:06:51 UTC (rev 4366) > +++ trunk/ChangeLog 2009-10-26 14:59:47 UTC (rev 4367) > @@ -8,6 +8,9 @@ > sciwrappers.h, build.h. (This helps to get compiler warnings for uses > of functions not in the API). > Warning: any plugins that include these headers should remove them. > + * src/build.c, src/build.h: > + Move function doc-comments to build.c so they stay in sync. Note: > + these functions are still not in the API. > > > 2009-10-25 Enrico Tröger <enrico(dot)troeger(at)uvena(dot)de> > > Modified: trunk/src/build.c > =================================================================== > --- trunk/src/build.c 2009-10-26 13:06:51 UTC (rev 4366) > +++ trunk/src/build.c 2009-10-26 14:59:47 UTC (rev 4367) > @@ -201,7 +201,7 @@ > gboolean printbuildcmds = PRINTBUILDCMDS; > > static GeanyBuildCommand **cl[GEANY_GBG_COUNT][GEANY_BCS_COUNT] = { > - /* GEANY_BCS_DEF, GEANY_BCS_FT, GEANY_BCS_HOME_FT, GEANY_BCS_PREF, > + /* GEANY_BCS_DEF, GEANY_BCS_FT, GEANY_BCS_HOME_FT, GEANY_BCS_PREF, > * GEANY_BCS_FT_PROJ, GEANY_BCS_PROJ */ > { &ft_def, NULL, NULL, NULL, NULL, NULL }, > { &non_ft_def, NULL, NULL, &non_ft_pref, NULL, &non_ft_proj }, > @@ -306,7 +306,7 @@ > gint below, gint *from) > { > /* Note: parameter below used in macros above */ > - > + > GeanyFiletype *ft = NULL; > gint sink, *fr = &sink; > > @@ -444,7 +444,23 @@ > } > > > -/* remove the specified command, cmd < 0 remove whole group */ > +/** Remove the specified Build menu item. > + * > + * Makes the specified menu item configuration no longer exist. This > + * is different to setting fields to blank because the menu item > + * will be deleted from the configuration file on saving > + * (except the system filetypes settings @see Build Menu Configuration > + * section of the Manual). > + * > + * @param src the source of the menu item to remove. > + * @param grp the group of the command to remove. > + * @param cmd the index (from 0) of the command within the group. A negative > + * value will remove the whole group. > + * > + * If any parameter is out of range does nothing. > + * > + * @see build_menu_update > + **/ > void build_remove_menu_item(GeanyBuildSource src, GeanyBuildGroup grp, gint cmd) > { > GeanyBuildCommand *bc; > @@ -462,7 +478,20 @@ > } > > > -/* get the build build command for the specified menu item */ > +/** Get the @a GeanyBuildCommand structure for the specified Build menu item. > + * > + * Get the command for any menu item specified by @a src, @a grp and @a cmd even if it is > + * hidden by higher priority commands. > + * > + * @param src the source of the specified menu item. > + * @param grp the group of the specified menu item. > + * @param cmd the index of the command within the group. > + * > + * @return a pointer to the @a GeanyBuildCommand structure or @a NULL if it doesn't exist. > + * This is a pointer to an internal structure and must not be freed. > + * > + * @see build_menu_update > + **/ > GeanyBuildCommand *build_get_menu_item(GeanyBuildSource src, GeanyBuildGroup grp, gint cmd) > { > GeanyBuildCommand *bc; > @@ -475,6 +504,21 @@ > } > > > +/** Get the @a GeanyBuildCommand structure for the menu item. > + * > + * Get the current highest priority command specified by @a grp and @a cmd. This is the one > + * that the menu item will use if activated. > + * > + * @param grp the group of the specified menu item. > + * @param cmd the index of the command within the group. > + * @param src pointer to @a gint to return which source provided the command. Ignored if @a NULL. > + * Values are one of @a GeanyBuildSource but returns a signed type not the enum. > + * > + * @return a pointer to the @a GeanyBuildCommand structure or @a NULL if it doesn't exist. > + * This is a pointer to an internal structure and must not be freed. > + * > + * @see build_menu_update > + **/ > /* parameter checked version of get_build_cmd for external interface */ > GeanyBuildCommand *build_get_current_menu_item(GeanyBuildGroup grp, gint cmd, gint *src) > { > @@ -1373,8 +1417,20 @@ > } > > > -/* Call this whenever build menu items need to be enabled/disabled. > - * Uses current document (if there is one) when doc == NULL */ > +/** Update the build menu to reflect changes in configuration or status. > + * > + * Sets the labels and number of visible items to match the highest > + * priority configured commands. Also sets sensitivity if build commands are > + * running and switches executes to stop when commands are running. > + * > + * @param doc The current document, if available, to save looking it up. > + * If @c NULL it will be looked up. > + * > + * Call this after modifying any fields of a GeanyBuildCommand structure. > + * > + * @see Build Menu Configuration section of the Manual. > + * > + **/ > void build_menu_update(GeanyDocument *doc) > { > gint i, cmdcount, cmd, grp; > > Modified: trunk/src/build.h > =================================================================== > --- trunk/src/build.h 2009-10-26 13:06:51 UTC (rev 4366) > +++ trunk/src/build.h 2009-10-26 14:59:47 UTC (rev 4367) > @@ -181,79 +181,14 @@ > > /* build menu functions */ > > -/** Update the build menu to reflect changes in configuration or status. > - * > - * Sets the labels and number of visible items to match the highest > - * priority configured commands. Also sets sensitivity if build commands are > - * running and switches executes to stop when commands are running. > - * > - * @param doc The current document, if available, to save looking it up. > - * If @c NULL it will be looked up. > - * > - * Call this after modifying any fields of a GeanyBuildCommand structure. > - * > - * @see Build Menu Configuration section of the Manual. > - * > - **/ > - > void build_menu_update(GeanyDocument *doc); > > - > void build_toolbutton_build_clicked(GtkAction *action, gpointer user_data); > > -/** Remove the specified Build menu item. > - * > - * Makes the specified menu item configuration no longer exist. This > - * is different to setting fields to blank because the menu item > - * will be deleted from the configuration file on saving > - * (except the system filetypes settings @see Build Menu Configuration > - * section of the Manual). > - * > - * @param src the source of the menu item to remove. > - * @param grp the group of the command to remove. > - * @param cmd the index (from 0) of the command within the group. A negative > - * value will remove the whole group. > - * > - * If any parameter is out of range does nothing. > - * > - * @see build_menu_update > - **/ > - > void build_remove_menu_item(GeanyBuildSource src, GeanyBuildGroup grp, gint cmd); > > -/** Get the @a GeanyBuildCommand structure for the specified Build menu item. > - * > - * Get the command for any menu item specified by @a src, @a grp and @a cmd even if it is > - * hidden by higher priority commands. > - * > - * @param src the source of the specified menu item. > - * @param grp the group of the specified menu item. > - * @param cmd the index of the command within the group. > - * > - * @return a pointer to the @a GeanyBuildCommand structure or @a NULL if it doesn't exist. > - * This is a pointer to an internal structure and must not be freed. > - * > - * @see build_menu_update > - **/ > - > GeanyBuildCommand *build_get_menu_item(GeanyBuildSource src, GeanyBuildGroup grp, gint cmd); > > -/** Get the @a GeanyBuildCommand structure for the menu item. > - * > - * Get the current highest priority command specified by @a grp and @a cmd. This is the one > - * that the menu item will use if activated. > - * > - * @param grp the group of the specified menu item. > - * @param cmd the index of the command within the group. > - * @param src pointer to @a gint to return which source provided the command. Ignored if @a NULL. > - * Values are one of @a GeanyBuildSource but returns a signed type not the enum. > - * > - * @return a pointer to the @a GeanyBuildCommand structure or @a NULL if it doesn't exist. > - * This is a pointer to an internal structure and must not be freed. > - * > - * @see build_menu_update > - **/ > - > GeanyBuildCommand *build_get_current_menu_item(GeanyBuildGroup grp, gint cmd, gint *src); > > BuildMenuItems *build_get_menu_items(gint filetype_idx); > > > This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site. > _______________________________________________ > Geany-commits mailing list > Geany-commits(a)uvena.de > http://lists.uvena.de/cgi-bin/mailman/listinfo/geany-commits >

2 7

ctrl+tab switching between tabs
by Liviu Andronic 01 Nov '09

01 Nov '09

Dear developers Recently Geany implemented ctrl+tab to switch between different tabs. 2009-05-13 Nick Treleaven * src/keyfile.c: Remember scribble cursor position. * src/keybindings.c, TODO: Implement Most-Recently-Used document switching when pressing Ctrl-Tab keybinding. (It's probably not perfect, but works OK). I wanted to know whether this is a key binding that GTK+ supports natively, or whether in-house, Geany-specific modifications were needed to get this working in Geany. Thank you Liviu -- Do you know how to read? http://www.alienetworks.com/srtest.cfm Do you know how to write? http://garbl.home.comcast.net/~garbl/stylemanual/e.htm#e-mail

4 5

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

Devel November 2009