Devel October 2010

devel@lists.geany.org

18 participants
31 discussions

Start a nNew thread

(no subject)
by Sergey Terlemezyan 29 Oct '10

29 Oct '10

Could you tell me how can I add my own plugin to the available plugins list?

3 2

Geany-plugins not building. Failure in Addons
by Jon Senior 28 Oct '10

28 Oct '10

I realised that I'd not rebuilt geany-plugins since my last upgrade and I was missing my TODO list! I downloaded the latest release and tried that, but got an error when building (From memory, the same as I'm getting now). I then grabbed the svn and tried that. The result is below. Geany version is 0.20 (svn >= r5339). Geany-plugins is the svn as of 28/10/2010 16h14 CEST. ./autogen.sh completed happily (some macro warnings at the start, but seemed to complete since configure was run). Running ./configure doesn't throw up any errors. System is Fedora 12 with few alterations (geany being an obvious exception). gcc 4.4.4 The problem appears to be related to the PLUGIN_SET_TRANSLATABLE_INFO macro (That's where the first error crops up). Any ideas? Trace follows: ****************************** [jon@jon-laptop geany-plugins]$ make make all-recursive make[1]: Entering directory `/home/jon/Projects/geany-plugins/geany-plugins' Making all in po make[2]: Entering directory `/home/jon/Projects/geany-plugins/geany-plugins/po' make[2]: Nothing to be done for `all'. make[2]: Leaving directory `/home/jon/Projects/geany-plugins/geany-plugins/po' Making all in addons make[2]: Entering directory `/home/jon/Projects/geany-plugins/geany-plugins/addons' Making all in src make[3]: Entering directory `/home/jon/Projects/geany-plugins/geany-plugins/addons/src' CC addons.lo addons.c:45: error: expected declaration specifiers or ‘...’ before string constant addons.c:46: error: expected declaration specifiers or ‘...’ before string constant addons.c:47: error: expected declaration specifiers or ‘...’ before ‘(’ token addons.c:48: error: expected declaration specifiers or ‘...’ before ‘(’ token addons.c:49: error: expected declaration specifiers or ‘...’ before string constant addons.c:50: error: expected declaration specifiers or ‘...’ before string constant addons.c: In function ‘PLUGIN_SET_TRANSLATABLE_INFO’: addons.c:54: warning: empty declaration addons.c:88: error: storage class specified for parameter ‘AddonsInfo’ addons.c:89: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘*’ token addons.c:94: error: storage class specified for parameter ‘ao_update_editor_menu_cb’ addons.c:95: error: storage class specified for parameter ‘ao_document_activate_cb’ addons.c:96: error: storage class specified for parameter ‘ao_document_open_cb’ addons.c:97: error: storage class specified for parameter ‘ao_document_save_cb’ addons.c:98: error: storage class specified for parameter ‘ao_document_before_save_cb’ addons.c:99: error: storage class specified for parameter ‘ao_document_close_cb’ addons.c:100: error: storage class specified for parameter ‘ao_startup_complete_cb’ addons.c:106: error: parameter ‘plugin_callbacks’ is initialized addons.c:108: warning: braces around scalar initializer addons.c:108: warning: (near initialization for ‘plugin_callbacks’) addons.c:108: warning: initialization from incompatible pointer type addons.c:108: warning: excess elements in scalar initializer addons.c:108: warning: (near initialization for ‘plugin_callbacks’) addons.c:108: warning: excess elements in scalar initializer addons.c:108: warning: (near initialization for ‘plugin_callbacks’) addons.c:108: warning: excess elements in scalar initializer addons.c:108: warning: (near initialization for ‘plugin_callbacks’) addons.c:109: warning: braces around scalar initializer addons.c:109: warning: (near initialization for ‘plugin_callbacks’) addons.c:109: warning: initialization from incompatible pointer type addons.c:109: warning: excess elements in scalar initializer addons.c:109: warning: (near initialization for ‘plugin_callbacks’) addons.c:109: warning: excess elements in scalar initializer addons.c:109: warning: (near initialization for ‘plugin_callbacks’) addons.c:109: warning: excess elements in scalar initializer addons.c:109: warning: (near initialization for ‘plugin_callbacks’) addons.c:109: warning: excess elements in scalar initializer addons.c:109: warning: (near initialization for ‘plugin_callbacks’) addons.c:111: warning: braces around scalar initializer addons.c:111: warning: (near initialization for ‘plugin_callbacks’) addons.c:111: warning: initialization from incompatible pointer type addons.c:111: warning: excess elements in scalar initializer addons.c:111: warning: (near initialization for ‘plugin_callbacks’) addons.c:111: warning: excess elements in scalar initializer addons.c:111: warning: (near initialization for ‘plugin_callbacks’) addons.c:111: warning: excess elements in scalar initializer addons.c:111: warning: (near initialization for ‘plugin_callbacks’) addons.c:111: warning: excess elements in scalar initializer addons.c:111: warning: (near initialization for ‘plugin_callbacks’) addons.c:112: warning: braces around scalar initializer addons.c:112: warning: (near initialization for ‘plugin_callbacks’) addons.c:112: warning: initialization from incompatible pointer type addons.c:112: warning: excess elements in scalar initializer addons.c:112: warning: (near initialization for ‘plugin_callbacks’) addons.c:112: warning: excess elements in scalar initializer addons.c:112: warning: (near initialization for ‘plugin_callbacks’) addons.c:112: warning: excess elements in scalar initializer addons.c:112: warning: (near initialization for ‘plugin_callbacks’) addons.c:112: warning: excess elements in scalar initializer addons.c:112: warning: (near initialization for ‘plugin_callbacks’) addons.c:113: warning: braces around scalar initializer addons.c:113: warning: (near initialization for ‘plugin_callbacks’) addons.c:113: warning: initialization from incompatible pointer type addons.c:113: warning: excess elements in scalar initializer addons.c:113: warning: (near initialization for ‘plugin_callbacks’) addons.c:113: warning: excess elements in scalar initializer addons.c:113: warning: (near initialization for ‘plugin_callbacks’) addons.c:113: warning: excess elements in scalar initializer addons.c:113: warning: (near initialization for ‘plugin_callbacks’) addons.c:113: warning: excess elements in scalar initializer addons.c:113: warning: (near initialization for ‘plugin_callbacks’) addons.c:114: warning: braces around scalar initializer addons.c:114: warning: (near initialization for ‘plugin_callbacks’) addons.c:114: warning: initialization from incompatible pointer type addons.c:114: warning: excess elements in scalar initializer addons.c:114: warning: (near initialization for ‘plugin_callbacks’) addons.c:114: warning: excess elements in scalar initializer addons.c:114: warning: (near initialization for ‘plugin_callbacks’) addons.c:114: warning: excess elements in scalar initializer addons.c:114: warning: (near initialization for ‘plugin_callbacks’) addons.c:114: warning: excess elements in scalar initializer addons.c:114: warning: (near initialization for ‘plugin_callbacks’) addons.c:115: warning: braces around scalar initializer addons.c:115: warning: (near initialization for ‘plugin_callbacks’) addons.c:115: warning: initialization from incompatible pointer type addons.c:115: warning: excess elements in scalar initializer addons.c:115: warning: (near initialization for ‘plugin_callbacks’) addons.c:115: warning: excess elements in scalar initializer addons.c:115: warning: (near initialization for ‘plugin_callbacks’) addons.c:115: warning: excess elements in scalar initializer addons.c:115: warning: (near initialization for ‘plugin_callbacks’) addons.c:115: warning: excess elements in scalar initializer addons.c:115: warning: (near initialization for ‘plugin_callbacks’) addons.c:116: warning: braces around scalar initializer addons.c:116: warning: (near initialization for ‘plugin_callbacks’) addons.c:116: warning: initialization from incompatible pointer type addons.c:116: warning: excess elements in scalar initializer addons.c:116: warning: (near initialization for ‘plugin_callbacks’) addons.c:116: warning: excess elements in scalar initializer addons.c:116: warning: (near initialization for ‘plugin_callbacks’) addons.c:116: warning: excess elements in scalar initializer addons.c:116: warning: (near initialization for ‘plugin_callbacks’) addons.c:116: warning: excess elements in scalar initializer addons.c:116: warning: (near initialization for ‘plugin_callbacks’) addons.c:118: warning: braces around scalar initializer addons.c:118: warning: (near initialization for ‘plugin_callbacks’) addons.c:118: warning: excess elements in scalar initializer addons.c:118: warning: (near initialization for ‘plugin_callbacks’) addons.c:118: warning: excess elements in scalar initializer addons.c:118: warning: (near initialization for ‘plugin_callbacks’) addons.c:118: warning: excess elements in scalar initializer addons.c:118: warning: (near initialization for ‘plugin_callbacks’) addons.c:118: warning: excess elements in scalar initializer addons.c:118: warning: (near initialization for ‘plugin_callbacks’) addons.c:123: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘{’ token addons.c:129: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘{’ token addons.c:135: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘{’ token addons.c:141: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘{’ token addons.c:146: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘{’ token addons.c:155: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘{’ token addons.c:165: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘{’ token addons.c:173: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘{’ token addons.c:182: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘{’ token addons.c:190: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘{’ token addons.c:198: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘{’ token addons.c:206: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘{’ token addons.c:214: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘{’ token addons.c:225: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘{’ token addons.c:282: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘{’ token addons.c:291: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘{’ token addons.c:369: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘{’ token addons.c:481: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘{’ token addons.c:106: error: declaration for parameter ‘plugin_callbacks’ but no such parameter addons.c:102: error: declaration for parameter ‘ao_editor_notify_cb’ but no such parameter addons.c:100: error: declaration for parameter ‘ao_startup_complete_cb’ but no such parameter addons.c:99: error: declaration for parameter ‘ao_document_close_cb’ but no such parameter addons.c:98: error: declaration for parameter ‘ao_document_before_save_cb’ but no such parameter addons.c:97: error: declaration for parameter ‘ao_document_save_cb’ but no such parameter addons.c:96: error: declaration for parameter ‘ao_document_open_cb’ but no such parameter addons.c:95: error: declaration for parameter ‘ao_document_activate_cb’ but no such parameter addons.c:93: error: declaration for parameter ‘ao_update_editor_menu_cb’ but no such parameter addons.c:88: error: declaration for parameter ‘AddonsInfo’ but no such parameter addons.c:494: error: expected ‘{’ at end of input make[3]: *** [addons.lo] Error 1 make[3]: Leaving directory `/home/jon/Projects/geany-plugins/geany-plugins/addons/src' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/home/jon/Projects/geany-plugins/geany-plugins/addons' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/home/jon/Projects/geany-plugins/geany-plugins' make: *** [all] Error 2

4 7

File type icons?
by Colomban Wendling 27 Oct '10

27 Oct '10

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. Before any deeper thoughts, I want to add a few technical details: I added MIME type for every built-in filetypes [1] (see below why). I think that anyway it's a good thing to have the MIME type since it may allow to e.g. filter file selection by MIME type rather that extension only [2], etc. So this might be interesting to keep even without filetype icons. I use g_content_type_get_icon() (GLib/GIO 2.14 AFAIK, but not sure) and g_content_type_from_mime_type() (ouch, GLib/GIO 2.18). The first is obviously useful, and the second is there because I didn't wanted to use g_content_type_guess() because I think it'd be slow, and because we already know the filetype. I have a fallback if not available, but it doesn't provide different icons for different file types (currently only file/directory icons). So, the problem is mainly the GLib version in use, 2.18, that is probably not really acceptable... but it isn't a real "feature" but rather a UI candy, so the fallback is perhaps fine. And finally, the current points that are problematic: When sidebar_openfiles_add() is called, it's very likely that the document's filetype isn't set yet, so no icon (or a default one). It only appears when an opened file is renamed, since it updates the entry and the filetype is set at this time. Not sure how to fix this, but I haven't investigated yet. Same applies for notebook tabs, but since I'm really not sure it's a good idea to add them, I didn't tried yet. So, before going further and fixing the things that don't work, what do you think of this? Would it be better with or without it? Regards, Colomban [1] Patch joined, 0001-Add-MIME-type-to-GeanyFiletype.patch. I have set the MIME type to text/plain when I didn't find the right one, but perhaps NULL would be better to denote that it isn't reliable. [2] Patch 0001-Add-MIME-type-filtering-in-file-chooser-dialog.patch

3 16

using ctrl+c in vte
by Liviu Andronic 26 Oct '10

26 Oct '10

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 -- Do you know how to read? http://www.alienetworks.com/srtest.cfm http://goodies.xfce.org/projects/applications/xfce4-dict#speed-reader Do you know how to write? http://garbl.home.comcast.net/~garbl/stylemanual/e.htm#e-mail

4 5

[PATCH] Ensure convert line endings before save
by Manuel Bua 25 Oct '10

25 Oct '10

Sorry for reposting this message but i just realized i didn't include the "[PATCH]" prefix in the subject of my previous mail to this list, so the original text follows: -------------------8<-------------------8<-------------------8<-------------------8< Hello all, i already searched for this feature, in case someone else was already working on it or if it simply was a bad idea to implement. For now, i haven't found anything nor something against it so i implemented this simple feature, that basically ensure no mixed line endings control characters (le-cc) will be saved in the document, patch is attached (i used the latest SVN head, 5089). Let me explain the use case: i'm currently working on a project where some of the files contains mixed line endings control characters, ie., some lines end with just CR, other with just LF: there is an easy way to convert everyone of these control charaters to something else via "Document->Set line endings->Convert and set ..." but this isn't something i always manage to remember to do and, better, i would like the editor to take care of that for me. So this patch add just that: in the "Preferences->Files->Saving files" dialog i added a checkbox and, if checked, the editor will always convert any le-cc to the one currently actively on the document via sci_get_eol_mode(doc->editor->sci). I also would like to propose a change in the way le-cc are presented to the user, but i'll do a new post eventually. Regards, Manuel -------------------8<-------------------8<-------------------8<-------------------8<

2 3

Unhide preferences
by Dimitar Zhekov 23 Oct '10

23 Oct '10

Hi, all, What do you think about creating a firefox-about:config-like interface for the hidden preferences? For example, a "Various" tab in the preferences dialog, with a "name value" list, a check button or a text entry (depending on the currenttly selected element), and a link to www.geany.org/manual/current/#hidden-preferences. That'll take some time to write, for example to check that all changes are applied immediately, but I'm willing to do it, if you think it's a good idea. The stash provides a good base for such an interface. -- E-gards: Jimmy

5 18

Scintilla Lua lexers for syntax highlighting
by Nick Treleaven 22 Oct '10

22 Oct '10

Hi list, A while ago Lex and I discussed improving custom filetypes, and the most promising thing was using Lua lexers. *This is not a clear idea for adding support yet.* Here follows snippets of the discussion and some new links at the end. On Thu, 23 Sep 2010 13:39:34 +0100 Nick Treleaven <nick.treleaven(a)btinternet.com> wrote: > > >> >> Some of my current work involves the customers domain specific > > >> >> language (DSL), forcing me to use EMACS since they have a mode for the > > >> >> DSL. > > >> > ... > > >> >> 3. Emacs is way more configurable due to elisp, thats why the mode to > > >> >> support the DSL was done in Emacs. Of course the requirement to write > > >> >> language support in C/C++ is a tagmanager/Scintilla requirement, but > > >> >> Geany inherits that problem. > > >> > > > >> > I think plugins can lex/highlight a document themselves through > > >> > Scintilla's APIs, but it may be a bit awkward adapting an existing > > >> > lexer for use by a plugin only. Although if a plugin wrapper for > > >> > Scintilla lexers is possible, it would be useful for all lexers Geany > > >> > doesn't include. > > >> > > > >> > There is a project that uses Lua scripts to lex quite a lot of > > >> > languages - a plugin using this for Geany might be a good idea. > > >> > > >> I don't know Lua but I guess it would be better than having to build a > > >> dynamic loadable library from C/C++. Can the GeanyLua plugin do any > > >> of this? I've only glanced at it? > > > > > > GeanyLua is for scripting, I was talking about a Scintilla Lua lexing > > > addon - apparently SciTE now has support for this: > > > > > > http://www.scintilla.org/ScriptLexer.html > > > > Interesting, I wasn't aware of this. Does it work in Geany? > > Geany has no support for it, I haven't looked at how SciTE does it. Found the original project that does this (the next version of SciTE will have support for this): http://code.google.com/p/scintillua/ http://code.google.com/p/scintillua/wiki/LexerList Haven't looked at it really but it mentions universal color schemes, so I'll investigate sometime - this could be useful for adding named styles. Nick

2 1

"Ensure new line on file end" inserts new line when file is empty
by Eugene Arshinov 22 Oct '10

22 Oct '10

I think it's a bug. I didn't notice it before as I usually use addons plugin with "Strip trailing blank lines" option checked. Patch attached, also modified to use utils_get_eol_char(). Best regards, Eugene.

3 14

What's the point of compiling geany without regex support?
by Jiří Techet 21 Oct '10

21 Oct '10

Hi, I started implementing the idea of indenting based on regular expressions and have noticed that geany can be compiled without regex support. Obviously in this case the indent thing wouldn't work. I don't quite understand when someone would want to compile geany without regex. By default in configure.ac you use the system regex library. If it doesn't exist, geany is compiled without regex support. Why not to automatically fallback to using the regex library shipped with geany when system regtex library is missing so there is always some regex support? This would also remove many ugly ifdefs from the geany's code. Cheers, Jiri

4 11

[PATCH] Add support for Erlang and (R5RS) Scheme
by Taylor Venable 20 Oct '10

20 Oct '10

Hello. In response to my own feature requests (2993016, 2993022) I've written basic support for Erlang and Scheme into Geany. For Scheme, I hijacked the Lisp lexer and changed a few things, such as the names of the keyword configurations. There should probably be more subtle changes to accommodate differences in the languages. For Erlang, I used the existing Scintilla lexer and hooked it into Geany. The patch at http://metasyntax.net/geany.diff can be applied to at least Subversion trunk r5303. Please let me know if this is welcome, and if so I'll put some time into refining the support, adding tag scanners, etc. -- Taylor C. Venable http://metasyntax.net/

3 4

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

Devel October 2010