Hello!
I tried to test Geany as much as possible to discover some issues before release. There are many bugs so I placed them into one big GitHub Gist.
Summary: - autoclose plugin disabling segfault (maybe geany core) - geanylatex bug with symbol replace - manu interface issues (see Gist) - geanylatex at close segfault (see Gist for backtrace and IRC for investigation) - shift column plugin doesn't work at all (orphaned plugin, but invalid plugin in release isn't good) - GeanyPy/GeanyLua probably should list their plugins in the main plugin list (it's hard to use scripts). Also why not have python in core?
Some design issues: - Adding plugin to Geany is very painful. Plugin creator should edit at least 14 (!!!) files spaghettized through whole project to do that. Also plugin creator should know two build systems (automake and waf). Possible solution - "onefile.c" plugin and "magic" command e.g. geany-make-plugin or geany-install-plugin. See GIMP for reference. - Lack of native scripting support. LuaJIT could be a _simple_ solution for that because of FFI interface and easy integration with C. Python also good but currently it's just plugin so not widely used. Also see GIMP plugin system for reference. One python script is enough to make plugin. - Plugins has MUCH copy-paste code: settings, help, keybindings. API simplification is possible I think. Creating simple wrappers will eliminate the GTK spaghetti.
See full list and crash dumps here: https://gist.github.com/scriptum/9949771
-- Best regards, Pavel Roschin aka RPG
I think there is more one bug, which I seen it some month ago. With vte 0.36 (GNOME 3.12 cycle) the terminal in the bottom don't work, and cause to crash. since it happen, I work with 'geany -t' (disable terminal).
I think each Arch's user will be affected from this bug, since GNOME 3.12 (with vte 0.36 and glib 2.40) it already in the testing repo, and in a week/two-weeks it will be available in the extra (stable) repo.
Regards, Yosef Or Boczko
בתאריך ד', אפר 9, 2014 בשעה 8:58 PM, Pavel Roschin roshin@scriptumplus.ru כתב:
Hello!
I tried to test Geany as much as possible to discover some issues before release. There are many bugs so I placed them into one big GitHub Gist.
Summary:
- autoclose plugin disabling segfault (maybe geany core)
- geanylatex bug with symbol replace
- manu interface issues (see Gist)
- geanylatex at close segfault (see Gist for backtrace and IRC for investigation)
- shift column plugin doesn't work at all (orphaned plugin, but
invalid plugin in release isn't good)
- GeanyPy/GeanyLua probably should list their plugins in the main
plugin list (it's hard to use scripts). Also why not have python in core?
Some design issues:
- Adding plugin to Geany is very painful. Plugin creator should edit
at least 14 (!!!) files spaghettized through whole project to do that. Also plugin creator should know two build systems (automake and waf). Possible solution
- "onefile.c" plugin and "magic" command e.g. geany-make-plugin or geany-install-plugin. See GIMP for reference.
- Lack of native scripting support. LuaJIT could be a _simple_
solution for that because of FFI interface and easy integration with C. Python also good but currently it's just plugin so not widely used. Also see GIMP plugin system for reference. One python script is enough to make plugin.
- Plugins has MUCH copy-paste code: settings, help, keybindings. API simplification is possible I think. Creating simple wrappers will
eliminate the GTK spaghetti.
See full list and crash dumps here: https://gist.github.com/scriptum/9949771
-- Best regards, Pavel Roschin aka RPG _______________________________________________ Devel mailing list Devel@lists.geany.org https://lists.geany.org/cgi-bin/mailman/listinfo/devel
On Wed, 09 Apr 2014 18:36:00 +0003 Yosef Or Boczko yoseforb@gnome.org wrote:
I think there is more one bug, which I seen it some month ago. With vte 0.36 (GNOME 3.12 cycle) the terminal in the bottom don't work, and cause to crash. since it happen, I work with 'geany -t' (disable terminal).
I think each Arch's user will be affected from this bug, since GNOME 3.12 (with vte 0.36 and glib 2.40) it already in the testing repo, and in a week/two-weeks it will be available in the extra (stable) repo.
Did you report it into bugtracker already? At least I'm reading for the first time about this.
Cheers, Frank
Sorry, but I didn't report this yet. I just asked about this in the geany irc channel.
Regards, Yosef Or Boczko
בתאריך ד', אפר 9, 2014 בשעה 9:51 PM, Frank Lanitz frank@frank.uvena.de כתב:
On Wed, 09 Apr 2014 18:36:00 +0003 Yosef Or Boczko yoseforb@gnome.org wrote:
I think there is more one bug, which I seen it some month ago. With vte 0.36 (GNOME 3.12 cycle) the terminal in the bottom don't work, and cause to crash. since it happen, I work with 'geany -t' (disable terminal).
I think each Arch's user will be affected from this bug, since GNOME 3.12 (with vte 0.36 and glib 2.40) it already in the testing repo, and in a week/two-weeks it will be available in the extra (stable) repo.
Did you report it into bugtracker already? At least I'm reading for the first time about this.
Cheers, Frank _______________________________________________ Devel mailing list Devel@lists.geany.org https://lists.geany.org/cgi-bin/mailman/listinfo/devel
On Wed, 09 Apr 2014 18:51:58 +0003 Yosef Or Boczko yoseforb@gnome.org wrote:
Sorry, but I didn't report this yet. I just asked about this in the geany irc channel.
Don't put such things into IRC. Never, please. It's just not visible.
Cheers, Frank
On Wed, 09 Apr 2014 18:51:58 +0003 Yosef Or Boczko yoseforb@gnome.org wrote:
Sorry, but I didn't report this yet. I just asked about this in the geany irc channel.
Don't put such things into IRC. Never, please. It's just not visible.
Cheers, Frank
Good point to create accessible bug tracker for Geany:) AFAIK you don't want use GitHub Issues so people report bugs elsewhere.
-- Best regards, Pavel Roschin aka RPG
On Wed, 9 Apr 2014 23:19:52 +0400 Pavel Roschin roshin@scriptumplus.ru wrote:
Good point to create accessible bug tracker for Geany:) AFAIK you don't want use GitHub Issues so people report bugs elsewhere.
sf is working for 99,9% of people ok ... ;)
(Sorry, github is the same stupid vendor locking as SF is. I will not move from one tracker with issues to another. Maybe sometime somebody will have the time to setup a own instance, it would be good. But to be honest, I didn't see some just working solution for years. They all suck at some point)
On 14-04-09 12:32 PM, Frank Lanitz wrote:
On Wed, 9 Apr 2014 23:19:52 +0400 Pavel Roschin roshin@scriptumplus.ru wrote:
Good point to create accessible bug tracker for Geany:) AFAIK you don't want use GitHub Issues so people report bugs elsewhere.
sf is working for 99,9% of people ok ... ;)
It's often not working right for me, losing comments, and being really slow.
(Sorry, github is the same stupid vendor locking as SF is. I will not move from one tracker with issues to another. Maybe sometime somebody will have the time to setup a own instance, it would be good. But to be honest, I didn't see some just working solution for years. They all suck at some point)
You can freely export bug tracker stuff out of both sourceforge and github, neither one really locks you in.
The thing with Github is you get better integration with source code, like closing bugs from commit messages, closing bugs when associated PRs are closed, linking with source code, and also it means users don't have to have to have multiple logins and stuff (same could be said for using Github wikis too). Also the UI is nicer to use IMO.
Cheers, Matthew Brush
On 10 April 2014 17:20, Matthew Brush mbrush@codebrainz.ca wrote:
On 14-04-09 12:32 PM, Frank Lanitz wrote:
On Wed, 9 Apr 2014 23:19:52 +0400 Pavel Roschin roshin@scriptumplus.ru wrote:
Good point to create accessible bug tracker for Geany:) AFAIK you don't want use GitHub Issues so people report bugs elsewhere.
sf is working for 99,9% of people ok ... ;)
Well, only 99.9% of the people that actually manage to make bug/feature requests. We just don't hear from the rest. :(
It's often not working right for me, losing comments, and being really slow.
Agree SF is terribly slow.
(Sorry, github is the same stupid vendor locking as SF is. I will not move from one tracker with issues to another. Maybe sometime somebody will have the time to setup a own instance, it would be good. But to be honest, I didn't see some just working solution for years. They all suck at some point)
Yes, all bug trackers suck in some way. Anybody wanna make a Geany bugtracker plugin? ;-)
You can freely export bug tracker stuff out of both sourceforge and github, neither one really locks you in.
Yes both can export JSON, and github can import it (I didn't look at SF import, I want out not in :-).
Simply use your favourite scripting language (eg Python) to convert one to the other.
The thing with Github is you get better integration with source code, like closing bugs from commit messages, closing bugs when associated PRs are closed, linking with source code, and also it means users don't have to have to have multiple logins and stuff (same could be said for using Github wikis
And github website, then Geany would only need its own server for sweetgeany :)
too). Also the UI is nicer to use IMO.
And easier to search, and waaaay faster.
Cheers Lex
Cheers, Matthew Brush
Devel mailing list Devel@lists.geany.org https://lists.geany.org/cgi-bin/mailman/listinfo/devel
Am 10.04.2014 09:37, schrieb Lex Trotman:
On 10 April 2014 17:20, Matthew Brush mbrush@codebrainz.ca wrote:
On 14-04-09 12:32 PM, Frank Lanitz wrote:
On Wed, 9 Apr 2014 23:19:52 +0400 Pavel Roschin roshin@scriptumplus.ru wrote:
Good point to create accessible bug tracker for Geany:) AFAIK you don't want use GitHub Issues so people report bugs elsewhere.
sf is working for 99,9% of people ok ... ;)
Well, only 99.9% of the people that actually manage to make bug/feature requests. We just don't hear from the rest. :(
It's often not working right for me, losing comments, and being really slow.
Agree SF is terribly slow.
(Sorry, github is the same stupid vendor locking as SF is. I will not move from one tracker with issues to another. Maybe sometime somebody will have the time to setup a own instance, it would be good. But to be honest, I didn't see some just working solution for years. They all suck at some point)
Yes, all bug trackers suck in some way. Anybody wanna make a Geany bugtracker plugin? ;-)
You can freely export bug tracker stuff out of both sourceforge and github, neither one really locks you in.
Yes both can export JSON, and github can import it (I didn't look at SF import, I want out not in :-).
Simply use your favourite scripting language (eg Python) to convert one to the other.
The thing with Github is you get better integration with source code, like closing bugs from commit messages, closing bugs when associated PRs are closed, linking with source code, and also it means users don't have to have to have multiple logins and stuff (same could be said for using Github wikis
And github website, then Geany would only need its own server for sweetgeany :)
github is not free -- even I like that page too. So who will sign, that you will be able to epxort bugs etc. in maybe 1 year, 2 years? This is what I mean when I say vendor lockin.
Cheers, Frank
[...]
github is not free -- even I like that page too. So who will sign, that you will be able to epxort bugs etc. in maybe 1 year, 2 years? This is what I mean when I say vendor lockin.
Of course, thats why we should keep off-site backups of the bugs and features and no matter which site we use (even our own) ... erm, we *are* keeping a backup of the bugs and features from SF aren't we? ;-)
At least the website and everything else is in git so every clone is a backup, ie the infrastructure and www.geany.org repos, wonder how many clones of those there actually are though?
Cheers Lex
Cheers, Frank _______________________________________________ Devel mailing list Devel@lists.geany.org https://lists.geany.org/cgi-bin/mailman/listinfo/devel
it means users don't have to have to have multiple logins and stuff
Agree.
Login issues with SF makes me crazy.
Also about that 99.9% people have no troubles - I assume this is a people that have SF account - they are lucky. But you just cannot get opinion from those who has no SF account (e.g. me:). I'm sorry but SF authentification system is BS. It's very buggy and slow. I used SF earlier through Google but recent time I lost my account because of changing authentification policy.
Unlike SF GitHub has good cross-site authentication system and I don't care about it.
-- Best regards, Pavel Roschin aka RPG
On 10/04/14 19:45, Pavel Roschin wrote:
it means users don't have to have to have multiple logins and stuff
Agree.
Login issues with SF makes me crazy.
Basically I share Frank's concern about Github, SF and other big players.
On the other hand, I fully agree with the others that SF just sucks nowadays and is a pain to use (we stopped using their file manager and download platform for Geany long time ago already because it became unusable, now the rest more or less followed :( ).
I'd actually vote for Github issue tracker for various reasons (integration with commits, code is already on Github, Github is a company yes, but it feels like most of the open source community hangs around on Github and it just works).
Self hosting a bug tracker could work but would cause additional efforts in choosing a suitable software, setting it up and maintaining it. Additionally, users again have to sign up on yet another site, keep logins and stuff.
BUT: maybe we could delay this discussion for a week or so until we got the 1.24 release into the wild :).
Regards, Enrico
Le 09/04/2014 20:33, Yosef Or Boczko a écrit :
I think there is more one bug, which I seen it some month ago. With vte 0.36 (GNOME 3.12 cycle) the terminal in the bottom don't work, and cause to crash. since it happen, I work with 'geany -t' (disable terminal).
I think each Arch's user will be affected from this bug, since GNOME 3.12 (with vte 0.36 and glib 2.40) it already in the testing repo, and in a week/two-weeks it will be available in the extra (stable) repo.
It's GTK 3.x, right? GTK 3 support is still not considered stable, so I guess we don't care for 1.24 -- and anyway GTK 3.9.something somewhat broke Scintilla display (it now flickers badly).
But, its weird a new version of the VTE lib would make us crash, unless they changed ABI?
Anyway, please report a bug to the appropriate place (hopefully, VTE :) if you can, and we'll take a look post 1.24.
Regards, Colomban
בתאריך ה', אפר 10, 2014 בשעה 2:18 AM, Colomban Wendling lists.ban@herbesfolles.org כתב:
Le 09/04/2014 20:33, Yosef Or Boczko a écrit :
I think there is more one bug, which I seen it some month ago. With vte 0.36 (GNOME 3.12 cycle) the terminal in the bottom don't work, and cause to crash. since it happen, I work with 'geany -t' (disable terminal).
I think each Arch's user will be affected from this bug, since GNOME 3.12 (with vte 0.36 and glib 2.40) it already in the testing repo, and in a week/two-weeks it will be available in the extra (stable) repo.
It's GTK 3.x, right? GTK 3 support is still not considered stable, so I guess we don't care for 1.24 -- and anyway GTK 3.9.something somewhat broke Scintilla display (it now flickers badly).
Alright, but I still use Geany with GTK+ 3, and I sure I'm not alone. To say 'it not stable, let this to be more unstable' it bad approach, but before I'll report a bug about this I can't say anything.
Btw, maybe the bug it because some changes in Glib 2.40 itself, not sure this come from vte 0.36.
Regards, Yosef Or Boczko
But, its weird a new version of the VTE lib would make us crash, unless they changed ABI?
Anyway, please report a bug to the appropriate place (hopefully, VTE :) if you can, and we'll take a look post 1.24.
Regards, Colomban
Devel mailing list Devel@lists.geany.org https://lists.geany.org/cgi-bin/mailman/listinfo/devel
Hi,
Regarding the plugin shiftcolumn,
- shift column plugin doesn't work at all (orphaned plugin, but invalid
plugin in release isn't good)
I am looking at this plugin, I know its kind of buggy but its not orphaned :). I dont know if this plugin is invalid maybe more experienced geany devs can comment on this.
Thanks, Shankhoneer Chakrovarty
Hi,
Thanks for the work, bad for putting all together in one big blob.
On Wed, 9 Apr 2014 21:58:59 +0400 Pavel Roschin roshin@scriptumplus.ru wrote:
- geanylatex at close segfault (see Gist for backtrace and IRC for investigation)
Will not search backlog of IRC. To much noise. What did you do to get this?
Cheers, Frank
On Wed, 9 Apr 2014 20:48:35 +0200 Frank Lanitz frank@frank.uvena.de wrote:
Hi,
Thanks for the work, bad for putting all together in one big blob.
On Wed, 9 Apr 2014 21:58:59 +0400 Pavel Roschin roshin@scriptumplus.ru wrote:
- geanylatex at close segfault (see Gist for backtrace and IRC for investigation)
Will not search backlog of IRC. To much noise. What did you do to get this?
Even I see what might could be the cause, I cannot reproduce it. I need more details please.
Cheers, Frank
On Wed, 9 Apr 2014 20:48:35 +0200 Frank Lanitz frank@frank.uvena.de wrote:
Hi,
Thanks for the work, bad for putting all together in one big blob.
On Wed, 9 Apr 2014 21:58:59 +0400 Pavel Roschin roshin@scriptumplus.ru wrote:
- geanylatex at close segfault (see Gist for backtrace and IRC for investigation)
Will not search backlog of IRC. To much noise. What did you do to get this?
Even I see what might could be the cause, I cannot reproduce it. I need more details please.
Cheers, Frank
This not actually reproducible. I enabled all plugins, after time Geany started to crash sometimes at exit.
This is IRC history about this bug:
https://gist.github.com/scriptum/10304696
In short: devhelp + geanylatex = crash at exit
-- Best regards, Pavel Roschin aka RPG
On Wed, 9 Apr 2014 23:17:02 +0400 Pavel Roschin roshin@scriptumplus.ru wrote:
On Wed, 9 Apr 2014 20:48:35 +0200 Frank Lanitz frank@frank.uvena.de wrote:
Hi,
Thanks for the work, bad for putting all together in one big blob.
On Wed, 9 Apr 2014 21:58:59 +0400 Pavel Roschin roshin@scriptumplus.ru wrote:
- geanylatex at close segfault (see Gist for backtrace and IRC
for investigation)
Will not search backlog of IRC. To much noise. What did you do to get this?
Even I see what might could be the cause, I cannot reproduce it. I need more details please.
Cheers, Frank
This not actually reproducible. I enabled all plugins, after time Geany started to crash sometimes at exit.
This is IRC history about this bug:
https://gist.github.com/scriptum/10304696
In short: devhelp + geanylatex = crash at exit
I assume it only happens, when a TeX file having focus on closing? I think for some reasons, and this is what b4n also mention on IRC, devhelp is destroying/changing the doc-pointer at some point.
On Wed, 9 Apr 2014 23:17:02 +0400 Pavel Roschin roshin@scriptumplus.ru wrote:
On Wed, 9 Apr 2014 20:48:35 +0200 Frank Lanitz frank@frank.uvena.de wrote:
Hi,
Thanks for the work, bad for putting all together in one big blob.
On Wed, 9 Apr 2014 21:58:59 +0400 Pavel Roschin roshin@scriptumplus.ru wrote:
- geanylatex at close segfault (see Gist for backtrace and IRC
for investigation)
Will not search backlog of IRC. To much noise. What did you do to get this?
Even I see what might could be the cause, I cannot reproduce it. I need more details please.
Cheers, Frank
This not actually reproducible. I enabled all plugins, after time Geany started to crash sometimes at exit.
This is IRC history about this bug:
https://gist.github.com/scriptum/10304696
In short: devhelp + geanylatex = crash at exit
I assume it only happens, when a TeX file having focus on closing? I think for some reasons, and this is what b4n also mention on IRC, devhelp is destroying/changing the doc-pointer at some point.
Not sure. It happens even with empty (few *.c files) Geany. But who knows what happens internally. I do not use Geany for TeX, so probably it crashes without TeX documents (probably because I don't remember all details). Currently I have all plugins disabled and crashes didn't appear.
-- Best regards, Pavel Roschin aka RPG
On Wed, 9 Apr 2014 23:57:49 +0400 Pavel Roschin roshin@scriptumplus.ru wrote:
On Wed, 9 Apr 2014 23:17:02 +0400 Pavel Roschin roshin@scriptumplus.ru wrote:
On Wed, 9 Apr 2014 20:48:35 +0200 Frank Lanitz frank@frank.uvena.de wrote:
Hi,
Thanks for the work, bad for putting all together in one big blob.
On Wed, 9 Apr 2014 21:58:59 +0400 Pavel Roschin roshin@scriptumplus.ru wrote:
- geanylatex at close segfault (see Gist for backtrace and
IRC for investigation)
Will not search backlog of IRC. To much noise. What did you do to get this?
Even I see what might could be the cause, I cannot reproduce it. I need more details please.
Cheers, Frank
This not actually reproducible. I enabled all plugins, after time Geany started to crash sometimes at exit.
This is IRC history about this bug:
https://gist.github.com/scriptum/10304696
In short: devhelp + geanylatex = crash at exit
I assume it only happens, when a TeX file having focus on closing? I think for some reasons, and this is what b4n also mention on IRC, devhelp is destroying/changing the doc-pointer at some point.
Not sure. It happens even with empty (few *.c files) Geany. But who knows what happens internally. I do not use Geany for TeX, so probably it crashes without TeX documents (probably because I don't remember all details). Currently I have all plugins disabled and crashes didn't appear.
I had some crash with devhelp at booth at CLT when I wanted to show somebody some feature. But wasn't able to reproduce. Maybe some timing thing?
On 14-04-09 01:15 PM, Frank Lanitz wrote:
On Wed, 9 Apr 2014 23:57:49 +0400 Pavel Roschin roshin@scriptumplus.ru wrote:
On Wed, 9 Apr 2014 23:17:02 +0400 Pavel Roschin roshin@scriptumplus.ru wrote:
On Wed, 9 Apr 2014 20:48:35 +0200 Frank Lanitz frank@frank.uvena.de wrote:
Hi,
Thanks for the work, bad for putting all together in one big blob.
On Wed, 9 Apr 2014 21:58:59 +0400 Pavel Roschin roshin@scriptumplus.ru wrote:
> - geanylatex at close segfault (see Gist for backtrace and > IRC for investigation)
Will not search backlog of IRC. To much noise. What did you do to get this?
Even I see what might could be the cause, I cannot reproduce it. I need more details please.
Cheers, Frank
This not actually reproducible. I enabled all plugins, after time Geany started to crash sometimes at exit.
This is IRC history about this bug:
https://gist.github.com/scriptum/10304696
In short: devhelp + geanylatex = crash at exit
I assume it only happens, when a TeX file having focus on closing? I think for some reasons, and this is what b4n also mention on IRC, devhelp is destroying/changing the doc-pointer at some point.
Not sure. It happens even with empty (few *.c files) Geany. But who knows what happens internally. I do not use Geany for TeX, so probably it crashes without TeX documents (probably because I don't remember all details). Currently I have all plugins disabled and crashes didn't appear.
I had some crash with devhelp at booth at CLT when I wanted to show somebody some feature. But wasn't able to reproduce. Maybe some timing thing?
Devhelp plugin shouldn't change document pointer, it only reparents the document notebook into another notebook, but it doesn't change its name and ui_lookup_widget() can still find it and such. Actually the concept is mostly copied from SplitWindow plugin which does something quite similar, so if you are running SplitWindow + Devhelp, I can almost guarantee some problems (although it really shouldn't *crash*, but rather spew assertion failures to terminal and just not work correctly).
The geanylatex bug I looked at from pastebin on IRC the other day looked to me like Scintilla's notification was firing after the GeanyEditor, GeanyDocument or GeanyFiletype was destroyed/re-used/whatever and it was dereferencing a NULL or invalid pointer.
Cheers, Matthew Brush
On Wed, 9 Apr 2014 21:58:59 +0400 Pavel Roschin roshin@scriptumplus.ru wrote:
- geanylatex bug with symbol replace
I can verify this, but note yet sure why this happen.
Cheers, Frank