I just made a test build of Geany Plugins 1.22 for Windows.
A little surprisingly for me, it all worked fine on the first attempt :).
I only had problems loading the Geany-Lua plugin with some strange error
message which I didn't investigate yet:
The error message occurs on plugin loading. I'm not sure whether it is
caused by my system or something else.
If anyone wants to test it, any feedback is appreciated.
... requires an existing Geany 1.22 installation.
Get my GPG key from http://www.uvena.de/pub.asc
I want to say, that it would be nice, if a DocumentMap/MiniMap would be added to Geany. Please add it to the Wishlist on your side.
Notepad++ have something called "Document Map":
Sublime Text have something called "MiniMap":
Since some time, Kate have a MiniMap, too:
All three have a line, where with very small fonts a bigger part of the document is shown and the current visible part of the Textarea have a colored background in the map.
But they differ in additional functionality of it.
Where Sublime Text only shows the MiniMap, Kate on the other side, can replace the scrollbar with it. And on Notepad++ it is a mix between the two. The scrollbar is still there, but you can click in parts of the Document Map, to jump to that position.
An additional point I want to mention, is a bug in your Webside-software.
As I wanted to add this wish to the wishlist, I clicked at the bottom of the page on "edit this page" of the line "(If you have another idea/wish which should be listed here, edit this page)".
Then it asks for a username and password. Because I don't have an account for it, and I find no place to register, I have somewhat input. After that it shows be an empty page and Geany.org was no longer available.
I thought, it would be an coincidental/hazard/fortuity/hap, that that happens.
But now there was again Geany.org reachable, then I tried it again. And again the Geany-side was after that down. :-(
So please update your Geany homepage software. Or it is really a very big coincidental/hazard/fortuity/hap, that in two times the Geany side goes in that time down, I tried to login there.
Matthew Brush <notifications(a)github.com> wrote:
> @elextr FWIW, the files `makefile.win32` and `win32env.mk` (and geanypy.nsis for the installer and README.win32 for the instructions) are needed for `src/makefile.win32` to be useful.
> @eht16 Any chance you could get some time to try getting the Waf build system working so it can be built on Windows?
Taking cause from Geanypy, there are 2 small problems with $subject:
- no header fiels are installed, or maybe they are copied somewhere
outside the $prefix. Copying the headers manually is OK.
- geany.pc contains paths with single backslashes, and plugins build
fails with "c:path1path2...: no such file or directory". Replacing
with forward slashes works. All other .pc files I've checked under
win32 use forward slashes.
I haven't tried the latest git though.
We have had a report on IRC that running geany on the windows command
line will only open files in the Geany install directory unless you
use the full path.
eg C:\somepath> geany somefile.txt
will open installpath\somefile.txt not somepath\somefile.txt.
And with the "Open new documents from the command line" option set it
creates somefile.txt in the install dir since it doesn't exist there.
Suspicion is falling on
As the most experienced windowser (and the committer of that change)
could you look at it please?
Code navigation in Python language is a pain due to the fact that the
action "go to symbol definition" on classes or methods don't go to the
actual definition, but rather heads to the import line at the top of the
file. I am a bit surprised that no one complains about that...
The guilty is the call to parseImports() in tagmanager/ctags/python.c.
I have disabled this line and this fixes the problem. Now, Python
navigation is behaving correctly.
I tried to make it configurable but it seems to be rather complicated to
reach (in a clean way) the ctags code from Geany's configurator.
Would it be possible to only delete the line in Geany's source code ? or is
anyone more interested in being redirected to the import line rather than
the actual definition ?
Two ideas for the Compiler tab open for consideration:
1) Since both C/C++ compilers (g++, clang++) now output little ^ characters
which are supposed to point to the place where they got confused, I suggest
that the compiler tab use a (real) monospace font by default, so the ^ is
in the intended place.
2) After a compile, the tab should be scrolled back to the top since,
AFAIK, most people clear up reported errors from the first to the last so
they can identify and skip consequential errors caused by a prior compile
Greetings from a newbie.
I've been using Geany for a few years as a general editor under Ubuntu.
I'm into program development for Microchip PIC processors, and have
recently started using a programming language called "Jal".
Jal is a Pascal-like language, but the syntax is different enough that
telling Geany to use the Pascal highlighter does not work.
I have the geany 1.23 source, and I've actually make some changes to the
VHDL scintilla lexer and filetypes.vHDL to handle folding and syntax
However, I would like to do a better job of supporting Jal. In
particular, I would like the symbol tree to be able to show the
variables and constants defined in a Jal program. Using the VHDL
filetype, Geany shows the functions and procedures (I did nothing to
cause this to happen), but not the variables.
Only some filetypes actually display variables. Basic, for example,
does, while Pascal does not.
I've no problems with making changes to the Geany code, but I've no idea
where to start with the display of variables and constants. The
scintilla lexers that I've seen, and the scintilla documentation do not
make it really obvious how one writes a lexer.
I would appreciate it if someone could point me in the proper direction
- what pieces of code should I be looking at?
Thanks for any guidance you can provide.
Orleans (Ottawa) Canada
I am new to Geany plugins and GTK development in general, and I'd like
to know some best practices (and how-to's) for a plugin I'm working
on. It does code folding, by level--that is, rather than folding all
of the code at once, just the top-level or second-level (or
third-level...). (This is very useful to me, as I can open a file and
get all the functions at a glance, or e.g. for a python class look at
all the function defs by folding the second level, and so on.) I did
so by essentially copying the folding code in Geany's fold_all
function, and then adding a submenu and keybindings to call the
I think this may be useful to others and I'd like to submit it to
geany-plugins, but I have a couple questions first:
1) The submenu is in the tools menu, but I feel it would be better in
the Document menu underneath the existing folding functions. Is this a
good idea, and if so, how to I get at the document menu (since I can't
2) I didn't set the keybindings since it's not recommended as it may
interfere with existing ones. Is there a way to set them if the given
key is not in use, or is that a bad idea?
3) In the actual folding code I used sci_get_fold_level (and a couple
other scintilla wrappers) which aren't in the plugin API so I gather
my plugin may break at some point. There doesn't seem to be a way
around this for what I want to do. Is this ok?
4) Is there another plugin out there that does this? I couldn't find one.
5) Would geany-plugins accept another plugin?
As discussed in the "Compiler tab suggestions" thread, Geany regex
error message parsing is buggy - it fetches the matching strings by
index, but GRegex indexes all subgroups, returning empty string for
the non-matching ones. So using | for alternatives does not work,
and parsing a set of strings like:
filename:line:column: warning: passing argument # of 'function' from
incompatible pointer type
In file included from filename:line,
filename:line:column: note: expected 'foo' but argument is of type 'bar'
is either impossible, or requires a very complex expression.
This is a regression caused by our switch to GRegex.
Fix attached. Of course, it's a simple loop skipping the non-matching
groups by their start position. Tested with both filename:line and