abrt version: 1.1.13 architecture: i686 Attached file: backtrace cmdline: geany /home/rianby64/Documents/Work/schemlev.ru/schemlev.ru/www/tpl/eng_index.tpl /home/rianby64/Documents/Work/schemlev.ru/schemlev.ru/www/tpl/eng_inner.tpl /home/rianby64/Documents/Work/schemlev.ru/schemlev.ru/www/tpl/index.tpl /home/rianby64/Documents/Work/schemlev.ru/schemlev.ru/www/tpl/inner.tpl component: geany crash_function: gtk_notebook_button_release executable: /usr/bin/geany kernel: 2.6.34.7-56.fc13.i686.PAE package: geany-0.19.1-1.fc13 rating: 4 reason: Process /usr/bin/geany was killed by signal 11 (SIGSEGV) release: Fedora release 13 (Goddard) time: 1286304314 uid: 500 How to reproduce ----- 1.Don't know 2. 3.
Created attachment 451745 [details] File: backtrace
Hi Andres, thanks very much for reporting this issue. Is there any chance to get this issue reproduced? Without the ability to reproduce the issue we will both be unable to help you or fix the issue, upstream as well as me as the Fedora Packager. Best Regards, Dominic
Hi Dominic, thanks you for reply my comment. But its a shame that I can't remember exactly what was that bug. Excuse me please. I'm very happy with Geany. Really, it's a nice editor. Combined with sshFS is a great tool to make great things. I've my opinions about how to improve Geany project. For example, my current project has MEL code. Is there any chance to set up custom templates for highlights? Thanks a lot, Andres Rios
It is, yes.But maybe there is a bit more effort needed for that. Since Geany is based on Scintilla it is a good idea to first have a look if Scintilla supports this and if not, request the support for MEL code as a feature there. When this is done the Geany developers usually automatically apply new Scintilla versions after some time. If you like to do this by yourself, I'd suggest to have a deeper look at the documentation section on http://geany.org/ and maybe subscribe to the Geany devel mailing list to ask the developers. They are very kind and cooperative from my experience. :)
*** Bug 682483 has been marked as a duplicate of this bug. ***
Since the original issue wasn't reproducible anymore, I'm closing this issue with this.