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?
Hi everybody !
I tried to code the feature request n°683.
It's the first time I make code for a such large project, so before I
commit let me know how I could improve my code.
Please, be nice with me :)
The diff file : http://pastebin.com/t4Ejs1Bd
I also see a little mistake in the makefile.win32, "-lgthread-2.0" appears
2 times, so I remove one :
- -lpango-1.0 -lgobject-2.0 -lgmodule-2.0 -lgthread-2.0 -lglib-2.0
-lgthread-2.0 -lintl \
+ -lpango-1.0 -lgobject-2.0 -lgmodule-2.0 -lgthread-2.0 -lglib-2.0
On the off chance that we might be converging on a release I did a
compile of the plugins with the usual options (-Wall -Wextra
This was on GTK2 since many still don't work for GTK3.
The results are not too bad really :)
To summarise, other than deprecations which will be discussed below:
codenav - 2 unused variables
debugger - 1 warning, useless test, probably inconsequential
geanygendoc - 2 warnings, extra switch case may be consequential,
geanysendmail - 3 const discarded warnings
multiterm - unused variable warnings in code generated by the valac,
and const discarded warnings
Unused functions and variables are probably inconsequential, unless
they are the result of a typo in the code meant to use them, they need
a quick check and correct.
Extra switch case may indicate a typo, needs checking.
Discarded const potentially is a problem, it may indicate that
something may try to modify literal strings, which may have undefined
behaviour. Sometimes library headers use char* when they should have
const char*, this is annoying, but it can usually be worked around.
But must be checked, including the ones generated by the Vala
The details are at http://pastebin.geany.org/76dfx/
Since this is with GTK2 there are no GTK deprecation warnings (except
in Vala, which seems to have decided that the whole of GTK2 is
deprecated), but Glib ones are starting to creep through, in threading
mostly. The problem with using the replacement functions is that
their existence depends on the version of glib on the target system,
not on the system Geany is compiled on. Using the new functions may
therefore result in nasty surprises for users of binary packages. Any
Le 19/02/2014 06:23, Flynn Milligan a écrit :
> So far as I can tell, you're an acceptable person to contact about this
> matter; if not, I'll try to find a better place to submit it.
It's acceptable, but you should rather ask development question on the
devel(a)lists.geany.org mailing list (that I just CC'd), so any developer
can see, answer and comment ;)
> The current fullscreen behaviour, as you know, is to keep the menu bar
> and tabs visible when fullscreen mode is activated. It seems to me that
> it would be more logical to hide these elements in fullscreen mode. I'm
> not well-versed in C, but I'd like to change this. What's the best way
> to go about doing so?
As I think Lex already mentioned on IRC, we already have means to hide
some extra elements, they just aren't triggered when entering fullscreen.
But anyway, the way to go is to extend ui_utils.c function
ui_set_fullscreen() to do any additional job needed.
Also, such behavior needs to be configurable -- you find that entering
fullscreen should hide other stuff, but not everyone might agree, so it
should be a setting.
For example, even if I understand you might try to get more screen space
for the editor component, I for myself don't think it's really any tied
to whether it's fullscreen or not. But OTOH, I have a 22" screen, so…
In October of last year, I made a request to Scintilla to add a new lexer to the Scintilla upstream component to support the DMAP language; the lexer was added to version 3.3.7 of Scintilla in December last year. Currently Scintilla is at version 3.3.9
In anticipation of an update to Geany to use Scintilla 3.3.7 or later, I'd now like to add a new filetype to Geany which leverages the new lexer. Back in October, I modified a few files in the build in order to support the new filetype. How do I go about making these modification available to the Geany nightly system so they will eventually end up in the next official release? Do I provide complete modified source, or a diff file showing the changes?
Once the new filetype is in place, I have a new plugin ready for release to manipulate the DMAP language. Do you know when Geany 1.24.1 (which I hope will include the new filetype) might make the scene?
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 ?