Devel October 2009

devel@lists.geany.org

10 participants
14 discussions

txt2tags tagmanager patch
by Forgeot Eric 17 Apr '10

17 Apr '10

Hello, do I need to add something for the patch to be included in the geany repository? I've seen you talked about some "filedefs/filetypes.*" configuration, does it mean it would replace such definitions in the future?

3 4

Geany 0.18 (configure.in) has hidden depends on 'which' utility.
by Erik Southworth 31 Mar '10

31 Mar '10

Just a normal build: but a strange configure error did occur. $$$ checking whether we are using the GNU C++ compiler... yes checking whether g++ accepts -g... yes checking dependency style of g++... gcc3 configure: error: No C++ compiler not found. Please install a C++ compiler. $$$ I found it's just a ``which`` in configure.in. QQQ # check for C++ compiler explicitly and fail if none is found, do this check # after AC_PROG_CXX has set the CXX environment variable which $CXX >/dev/null 2>&1 if test "x$?" != "x0"; then AC_MSG_ERROR([No C++ compiler not found. Please install a C++ compiler.]) fi QQQ I didn't know that the ``which`` utility was considered a compiler. :p How about just using a shell builtin, ``hash``, ``type -P`` or just ``eval $CXX --version`` as a test instead? ------------------------------------------------------------------ configure.in:18 : which $CXX >/dev/null 2>&1 configure.in:51 : GIT=`which git 2>/dev/null` configure.in:60 : SVN=`which svn 2>/dev/null` Found 3 matches for "which". -- -Erik S

5 11

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

16 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

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

Build system glitches
by Enrico Tröger 28 Oct '09

28 Oct '09

Hey, I noticed a few more smaller and bigger problems with the new Build system: See attached image build_dialog_py_initial.png: this is the initial build settings dialog for an opened Python file. So far it looks fine except the "null" values for two Make commands. Then I changed the Python Compile and Run commands to use python2.5 instead of just python. Worked fine. But then, I opened the Build settings dialog for a XML file and for some reason, it shows me the Python Run command as Run command for the XML file. And it does this probably for each other filetype as well, tested also with Shellscript and I got again the Python Run command. This completely contradicts the original idea of the build system: being easy to use to compile&run single files. Not sure whether this is a bug or actually intended behaviour of your code, but it is not what Geany should do and it is not what Geany did before! Run commands were and should be filetype-dependent except you have opened a project and the project has a Run command defined. Furthermore, the Compile button is disabled in the toolbar. But this seems to be a separate issue :). The reported issues happened with latest Geany from SVN, a clean config (geany -c /tmp/test) and without a project being opened. Regards, Enrico -- Get my GPG key from http://www.uvena.de/pub.asc

4 20

Geany Plugins 0.18
by Chow Loong Jin 26 Oct '09

26 Oct '09

Hi all, Now that pretty much all changes for Geany Plugins 0.18 have been merged into the 0.18 branch, I'd like to make a release in ~24 hours. If anyone else has anything to add, please do it before then. If you need more time, please e-mail me or ping me on #geany in irc.freenode.net. -- Kind regards, Chow Loong Jin

1 0

Custom Filetypes
by Lex Trotman 22 Oct '09

22 Oct '09

Hi Nick, Enrico, I've got a question about how your custom filetype functionality will work when its available, specifically if it will do the following: For the builders WAF and SCONS the config files are actually pieces of python so they need to: - detect the custom filetype from the filename (not extension) (SConstruct and SConscript for SCONS and wscript for WAF) - use python lexers and highlighting - load tags for the functions provided by SCONS or WAF so tooltips work - since the config files are not a complete python program they should not have python compile and run commands, but at least SCONS could have a compile that is "scons --dry_run" and I'm sure WAF has a similar option. This will automatically work with the new build system so long as the custom filetype functionality creates a separate GeanyFiletype for the custom type and there is a suitable config file. Cheers Lex

3 9

Re: [Geany-devel] Nightly build failed: Plugins Windows build
by Frank Lanitz 18 Oct '09

18 Oct '09

On Sun, 18 Oct 2009 03:51:58 +0000 (UTC) noreply(a)nightly.geany.org wrote: > ../../plugins_svn/po/tr.po:8:43: syntax error > /usr/bin/msgfmt: found 1 fatal error > Build failed > -> task failed (err #1): > {task: po tr.po -> tr.mo} Fixed with r1014. Sory. Frank -- http://frank.uvena.de/en/

1 0

Geany.txt cleanup
by Lex Trotman 13 Oct '09

13 Oct '09

Hi All, Attached is a patch providing some cleanups for geany.txt. NOTE: There are a few TODOs in the file that need to be checked before the geany.html is re-created (Addons plugin compatible :-). These are things that I didn't know the answers to. I have minimised the reflows I applied, so that the patch didn't become too big, Some more wouldn't hurt but they are not critical. There are images called out in geany.txt that are missing from the doc/images directory. I have not created those because I can't seem to get a theme that looks like the other images, so someone who can generate screen captures that match the existing ones should do it. Cheers Lex

4 14

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

Devel October 2009