Péter | 8 Apr 13:46 2015

[Geany-Users] Syntax highlight, C-like

Is there only 2 groups of keywords? In C-like files.

(filetypes.Xxx.conf, tag_parser=C, lexer_filetype=C, [keywords], primary, secondary)


Users mailing list
Users <at> lists.geany.org
Rajendra Prasad | 2 Apr 06:50 2015

[Geany-Users] Help: python output console closing immedialtly


    I am using geany 1.24 with python 2.7 on windows7.
Problem: When i execute the python program immediately after installation, It running good with out any problem. But if I execute after closing the Geany at least once, it first opens the windows command window, then asks permission to execute python. Then the program executes and two windows will be opened. One of it will close so fast that I can not read anything from it. the second window shows the message press enter to continue...........

    When I have added, raw_input() at the end of the program, the first window stood still on successful execution of the program only, but not in the other instances.

   I tried in interne to find solution. But I am not able to trace what has to be done.

Thank you.
Users mailing list
Thomas Martitz | 29 Mar 00:23 2015

[Geany-Users] My non-C plugin roadmap


I was asked to share a bit about my roadmap regarding plugins. I'll try 
to give you a better idea with this post.

My ultimate goal is to implement a clean and maintainable way to support 
non-C plugins, preferably using existing widely used techniques. I 
concluded that libpeas[1] in conjunction with gobject-introspection can 
provide the base for this. Since Geany is not at all prepared for this I 
have several infrastructure which I do want to get merged into Geany. 
When Geany core is sufficiently setup for this, the non-C plugin 
enablement can happen outside the core, as a plugin, to stabilize there.

So, here's the set of infrastructure changes for the core. Please let me 
stress that all of this will happen in backward-compatible manner, no 
existing plugins break as part of this.

- linkage-cleanup (PR#429) - This changes the way plugins access Geany 
API functions. Instead of exporting a pointer to a struct of structs of 
API function pointers, now the APIs are exported directly. This work 
also includes an effort to stop exporting all function (we do this 
currently as a workaround to allow gtkbuilder to work), so *only* API 
function are exported and plugins cannot call internal function anymore. 
This change is also required to allow gobject-introspection to find 
geany functions at runtime (through g_module_symbol()) in the future.
- new API functions for registering keybindings (PR#376). The current 
API functions do not allow context information to be stored and passed 
to the key handler function. This makes it very hard for non-C plugins 
to use these function. So what's  needed are key handlers that get the 
necessary context information. This allows interprepted language plugins 
to register keybindings.
- A new plugin loader mechanism (a thread about this is already running 
on the devel list): Similarly to the keybindings, the plugin_* functions 
implemented by plugins do not carry any context information, making it 
hard for non-C plugins to implement them properly. Therefore a new 
loader mechaism is needed so that the context information can be passed. 
The loader works such that an API function is called to register a 
function pointer table. This is crucial to possibly support plugins that 
register other plugins (so called pluxies) which is simply not possible 
with the current mechaism. The current loader is kept for backwards 
compatibility (but will not receive new features).
- New API functions to allow plugins to act as proxy plugins (pluxies). 
These pluxies can then implement whatever is needed to execute code in 
the in the actual plugin, like invoking an interpreter or firing up a 
java vm. The pluxies call the new loader's API function on behalf of the 
actual plugin. The API function to implement the pluxies is a simple 
geany_register_pluxy() that, much like the normal plugin loader, that 
pluxies use to pass a function pointer table which implements the 
necessary hooks (probe(), load() and unload())

Once this is in place in the core, my roadmap contains the following 
items, which are implemented (at least initially) in a plugin, so no 
further changes to the cure should be necessary.
- Modify geanypy to use the new pluxy APIs. This will finally enable 
geanypy to show the python plugins in the normal PM dialog and support 
- Create a new pluxy that supports libpeas-based plugins (codename: 
peasy). Peasy will use libpeas to load plugins and their metadata.
- Part of the peasy work is also work on creating vala and 
gobject-introspection bindings for Geany's API functions, so that we can 
support python, javascript and lua out of the box.

This is my roadmap so far. It changed quite a bit since I started this 
non-C-plugins effort a year ago, but I hope it will be good for 
everyone. Please share your opinions on this or ask questions.

Best regards.
James Brierley | 19 Mar 17:26 2015

[Geany-Users] Lisp improvements

Hi all.

Geany has been as good to me over the past year or two of Lisping as it 
was with anything involving curly braces, but I would be interested in 
writing/contributing code to improve the support for tagging and 

Unless I’m doing something horribly wrong, Common Lisp is not supported 
by the symbol list out of the box the way that Python or C files are. 
So, I take it I would need to write a parser of the type under 
tagmanager/ctags in git — there isn’t one for Common Lisp at present. Is 
this correct? Syntax highlighting for Lisps (for what syntax there is) 
works fine but I would like to work on making the symbol list functional 
as well.

Take care,



James Brierley

Hate democracy? All the more reason to vote: http://bit.ly/1ErcOTx
7th May 2015 | #AnyoneButUkip | Save Britain, save yourself!
Users mailing list
Users <at> lists.geany.org
Lex Trotman | 17 Mar 23:18 2015

[Geany-Users] Communication reminder

Reminder to all those who are discussing changes that affect others,
like APIs or UIs.

Please discuss the changes on the ML not exclusively on IRC, not
everyone monitors IRC, and time zone issues mean not everyone is able
to contribute.

Do not discuss it on IRC and then dump it on the ML as a decided thing.

Yes the ML slows down the communication process, but then that's
probably a good thing anyway.  Deciding the first thing someone thinks
of is not always the best thing.

Matthew Brush | 12 Mar 10:20 2015

[Geany-Users] ANN: Overview Plugin (Minimap)

Hi all,

I made a plugin that puts one of those little zoomed-out scrollable 
mini-views into Geany, similar to Sublime Text's minimap. It's quite new 
but I think most of the bugs are worked out. If you wanna try it out or 
see it, you can from here:


Matthew Brush
Alessandro Pasotti | 11 Mar 17:45 2015

[Geany-Users] geany on hidpi screen


I'm using Geany on Kubuntu with an hidpi 4k screeen, it works fine
except for the tab close icons and the tree icons (both in the code
window for fold/unfold and the files tree).

Is there any setting for those icons size?


Alessandro Pasotti
w3:   www.itopen.it
Ongun Arısev | 6 Mar 12:21 2015

[Geany-Users] Reverting Geany color scheme to default


I would like to revert the Geany color scheme to the default one that it has when it is installed on the system. How can I do so? Furthermore, is there an easy way to download and change the color schemes? I always got confused when I tried to do it with Geany.

Many thanks,

Ongun Arısev
Users mailing list
Péter | 3 Mar 18:36 2015

[Geany-Users] Matching brace, colon inside

Geany does not find some rather obvious brace pairs. I edited my .bashrc file. Its recognized filetype is
"Config file" 
(I do not know, why.)

For testing, paste this text into an empty file, and issue a "Set Filetype"/Miscellaneous/"Config file" command.

The matching pair sometimes is found, sometimes isn't:

aa {}     good
aa []     good
aa ()     good
aa {:}    bad
aa [:]    bad
aa (:)    bad
  {:}      good
  [:]      good
  (:)      good
{:}       bad
[:]       good
(:)       bad



Users mailing list
Users <at> lists.geany.org
Richard Mindorff | 13 Feb 20:34 2015

[Geany-Users] debugging while interacting with program

When using the komodo ide for php I could interact with my program, putting
in data and using checkboxes and other HTML controls while debugging the
code in the IDE.
I would like to do the same thing for a C project. Geany uses GTK+ which has
controls. Can I interact in some terminal  while debugging in the geany ide?
Can I use other libraries like allegro to get controls that I can interact with?
Jiří Techet | 30 Jan 17:18 2015

[Geany-Users] The future of the GeanyPrj plugin


me again :-). With other Geany developers we have been discussing the future of the GeanyPrj plugin. The problem is the original developer behind it has abandoned the project so it is unmaintained now. There are several things we could do:

1. Nothing - i.e. keep it in the plugins repository unmaintained.

2. Somebody volunteers to maintain it (anyone?).

3. The plugin will be removed from the geany-plugins repository.

I would like to discuss the option (3) - while I haven't used the plugin myself much, I think the main reason people were using it was you could see multiple projects in the sidebar (and have them indexed). This is however possible with my ProjectOrganizer plugin now (see the announcement) so the question is whether there is any other use for the plugin. Otherwise I believe ProjectOrganizer offers many more features and displays the project files better so at least from my point of view (which may be biased), I think ProjectOrganizer is more or less a superset of GeanyPrj. (One exception is that with ProjectOrganizer you have to create projects explicitly while with GeanyPrj there's just kind of implicit project specification by pointing it to the directory where you keep projects).

So my preferred choice is (3) but if someone still finds the plugin useful and uses it, we can keep the plugin in the repository.


Users mailing list