I just wanted to remember you about #geany at freenode.net
Channel is open for everybody who wants to chat about Geany or topics
related to ;)
See you there,
Frank Lanitz <frank(a)frank.uvena.de>
GeanyLua 0.7.0 is out, with the following enhancements
and bug fixes:
* Support for Geany's new built-in keybinding API.
* Autotools scripts to support Geany's new pkg-config feature.
* Code cleanup to quiet some compiler warnings.
* Fix to compile with -DGEANY_DISABLE_DEPRECATED flag.
* New function: optimize() to speed up CPU-intensive scripts.
* Fixed a crash bug in the pickfile function's filter-parser.
* Fixed a compatibility problem with the GeanyDebug plugin.
* Fixed missing symbols bug in Win32 plugin.
* Added a copy of "Lua Short Reference" to the GeanyLua docs.
* Added a couple of new demo scripts.
Get it from:
First of all, I want to say to the developers of Geany that this is a
very impressive piece of software! I am amazed that I have not
discovered it until recently, because it is really too good to have
such (relatively) little exposure.
The problem I'm having is this: I'm not getting automatic indentation
for Python files (it seems to be working as described for C++). I
have searched the SF bug tracker, changelog, and this mailing list,
and found no mention of this problem.
In fact, all I found was great stuff about how Python indentation was
being improved (to recognize comments after a colon, for example),
which I was looking forward to seeing in action.
I am using Geany 0.13 on Windows XP Home. My autoindent mode is
"Current chars" and is on, and the status bar shows that the file is
indeed recognized as Python.
Hi all plugin authors,
I've just merged plugin keybindings support into the trunk. This allows
plugins to add configurable keybindings which are set just like Geany
To do this it was necessary to break the keybinding commands into
groups, so the plugin API has now broken for any plugins using
p_keybindings->send_command(). The good news is that by grouping
keybindings the plugin ABI can stay stable when we add any keybindings
to the core.
For the details on how to add keybindings to your plugins please see
plugins/htmlchars.c, and post here if you need more information.
Basically you use the new PLUGIN_KEY_GROUP macro to declare a
keybinding group, then initialize each keybinding in init() using
since the 2.6 API docs on www.gtk.org seems to not be available
anymore, I put them on http://geany.uvena.de/manual/gtk/ for reference.
These docs are meant for people who want to write plugins for Geany or
want to modify Geany's source code.
Obviously you can also use the current API docs for these libraries.
But using the 2.6 docs of the GTK libs (including GLib, GDK and Pango)
has the advantages that you don't get confused by any newer API
additions and you don't have to take care about whether you can use
them or not.
This is because Geany depends on GTK 2.6. API symbols from newer
GTK/GLib versions should be avoided to keep the source code building
against GTK 2.6. Therefore the offer of the outdated docs.
Plugins authors doesn't have to keep their plugins compatible with GTK
2.6, but maybe they want to because Geany does.
To make a long story short:
if anyone wants to use GTK 2.6 docs, you can find them on
Get my GPG key from http://www.uvena.de/pub.key
Here is new plugin for geany - geanydoc. You need SVN version of geany to compile it.
geanydoc allow execute specified commands on the current word near the cursor position. This word is passed as an argument to these commands. It allow either place output of these commands in geany buffer *DOC* or just execute external program. Geanydoc is intended to be used for searching documentation API in different sources.
This plugin do job similar to Content Action in geany core. Main differences:
1) It is designed specially to search documentation. And contains sane (IMHO) default configuration for doing this job. It is easier to edit this plugin settings to suit your documentation needs then setup bunch of hidden options for Content Action from scratch.
2) It allow to search documentation in different sources. (Example: For C if word was not found in man 2,3 page it will be searched in devhelp)
3) Allow to place output of documentation command in geany buffer *DOC*. (read: easy integration with console documentation tools such as "man")
plugin web page: http://users.cosmostv.by/yurand/geanydoc/
download 0.1 version: http://users.cosmostv.by/yurand/geanydoc/geanydoc-0.1.tar.gz
git repository: http://repo.or.cz/w/geanydoc.git
Yura Siamashka <yurand2(a)gmail.com>
OK, so I'll just use Geany to prepare a patch file for me. (duh!) Nice
One more note on operation. It handles typing fine (inserting &
deleting) but won't paste some text in multiple lines. That would be
nice; and a downstream goal.
The typing part is 95% of what I need to do anyway.
'Find in files' also finds <subject> in version control files and
directories like '.svn/text-base', '.svn/entries', etc...
It would be very handy if Geany would have a 'Exclude version control
files/dirs' checkbox in the 'Find in files' dialog (which even can be
enabled by default)
I'm no grep expert, but --exclude .svn isn't sufficient to hide all .svn
entries in the message window(?)