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?
cc_insert_custom_command_items() attempts to assign a key to the first
three "Send Selection to -> ..." commands even if no key is specified,
"(geany-bin:17617): Gtk-CRITICAL **: IA__gtk_accel_group_connect:
assertion `accel_key > 0' failed"
git patch attached.
I've been out of the loop for a while, but have just caught up with this thread and the one about Vala. Just wanted to add $0.02:
- I'm not really a C programmer (Java background), so would welcome non-C opportunities for plugin writing. Although I actually do like Lua scripting.
- Scintilla may be ugly compared to GtkSourceView, but my experience of their respective editors (eg Notepad++) is that it provides more features - and worthwhile ones. Even code folding is a plugin in Gedit. And I love rectangular selection. So I don't like the idea of swapping to GtkSourceView.
On Mon, Dec 2, 2013 12:54 PM AEDT Lex Trotman wrote:
>Just a note I am still summarising the thread, but "real life" is getting
>in the way. Real soon now (hopefully).
If I enable 'Override Geany keybindings' in Preferences-Terminal, and then disable it again, I can't use Alt+letter to open menus, nor Ctrl+Q to quit, until I close Geany and restart it.
Is this a known issue? I couldn't find an earlier discussion of it.
utils_strtod() has an **end output argument, like strtod(), but never
uses it. Of course, all callers pass NULL, so it doesn't matter much,
but it'll still be good to fix it.
Do you thing we shall handle the argument, or remove it? Assignind to
*end doesn't make much sense, since on successful utils_strtod(), *end
(if any) will always point to the end of the input string.
Recently there have been a number of proposals for significant changes in
Geany, different languages, GObjectification and other various changes.
As good or bad as the individual suggestions may be, they have made it
clear to me that there is no plan for the future of Geany that allows them
to be evaluated effectively.
So I am starting this thread to try to get ideas on where Geany should be
To start the ball rolling, here are some of the things I see Geany should
1. An architecture that allows multi-threading to be used for non-GUI
tasks. The most obvious of course is parsing. At the moment none of the
parsers support symbols in anything other than the global scope, and adding
them would significantly increase the parsing effort, but doing it in a
background thread would make the performance hit less obvious. But there
needs to be a careful design of the passing of data from the edit buffer to
the parser and back to the symbol tables to minimise overhead, latency and
ensure its non blocking. With such an architecture other complex
functionality can then also happen in the background without impacting
Geany's responsive feel.
2. Language specific assistance, such as indentation, or dynamic error
marking and intelligent autocompletes. I consider that these hang off the
previous capability of better parsing/analysis of the program. Matthew has
demonstrated a prototype that provides some of these facilities using
libclang (for the clang languages only C, C++, Obj-c). But the current
Geany architecture does not support plugging such things in easily, and
with the number of languages that Geany supports, I would suggest that its
small, light and fast tag would be severely threatened if assistance for
all languages were plugged in at once.
3. Proper portability. At the moment Geany is really a Linux application
that has some limited (and buggy) support for Windows. The main editing
widget that Geany uses is available for many platforms and toolkits. If
Geany had an architecture that separated the target specific parts into a
"backend" the way Scintilla does, then it would be possible to support
multiple targets more easily, making Geany less at the mercy of one
toolkit's direction (that means you deprecating GTK) and better able to
support different platforms like OSX and Windows. Work such as that
Dimitar is doing for spawning on Windows naturally then falls into such a
4. Multiple top level windows. As monitors are cheaper, being able to
spread views of files to optimally utilise the screen space available adds
to the users effectiveness. Most languages support multiple modules in
different files and many use multiple files for related parts, such as
C/C++ header and body. Looking at and editing several places/files at once
has many uses. As useful as splitwindows one and two are (especially
together) they still assume a single rectangular top level is available for
subdivision. But different desktop menu layouts or having other
applications visible at the same time can limit the contiguous rectangular
space available. Multiple top levels can make better use of
These are all big changes that don't fall into the current Geany mode of
"light maintenance and extra features as someone implements them". For big
changes like those above however, a clear design and a planned process is
needed to ensure that the big changes don't clash with each other and that
they are not derailed by interim smaller changes.
I would suggest the process to be:
1. gather other major ideas for capabilities that Geany should plan to
2. develop a design that supports these (or at least the most useful ones)
3. look at how that design can be implemented, can the existing design be
mutated to it, or is it a clean framework that large parts of the existing
functionality can plug into, or is it a whole clean implementation. This
also includes issues like languages to use (C, C++, Vala, Haskell etc).
4. depending on the outcome from 3. use a new repository organisation or at
least a new branch in the existing Geany repo to ensure that the existing
Geany is not destabilised by major changes as they take place.
This is something very different to the way Geany is currently operating,
and I don't know if the community wants to consider such a more structured
approach. If its felt that its worthwhile then I suggest that steps one
and two are best achieved using the wiki and I will volunteer to set up and
maintain page(s) for those phases at least.
So to summarise, what capabilities should Geany aspire to support, and what
is the process to develop the best software architecture to support those