Since a few days, I experienced crashes in Geany.
I didn't find a way to reproduce it yet, mostly it happens after switching from another workspace back to the workspace where Geany is running. If the crash happens, it occurs directly after switching to the workspace with Geany.
Here is the backtrace:
```
Starting program: /usr/bin/geany
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x7fffef631700 (LWP 26983)]
[New Thread 0x7fffeee30700 (LWP 26984)]
[New Thread 0x7fffd39cd700 (LWP 26985)]
[New Thread 0x7fff930c8700 (LWP 26986)]
Vector smash protection is enabled.
[New Thread 0x7fff8b034700 (LWP 26989)]
[New Thread 0x7fff8a833700 (LWP 26990)]
[New Thread 0x7fff8a032700 (LWP 26991)]
[New Thread 0x7fff89831700 (LWP 26992)]
[New Thread 0x7fff88c30700 (LWP 26993)]
[New Thread 0x7fff73fff700 (LWP 27035)]
[New Thread 0x7fff737fe700 (LWP 27036)]
[New Thread 0x7fff72ffd700 (LWP 27037)]
[New Thread 0x7fff727fc700 (LWP 27038)]
[New Thread 0x7fff71ffb700 (LWP 27039)]
[New Thread 0x7fff71186700 (LWP 27042)]
[New Thread 0x7fff70985700 (LWP 27043)]
[New Thread 0x7fff5bfff700 (LWP 27044)]
[New Thread 0x7fff5b7fe700 (LWP 27045)]
[Thread 0x7fff727fc700 (LWP 27038) exited]
[Thread 0x7fff5bfff700 (LWP 27044) exited]
[Thread 0x7fff72ffd700 (LWP 27037) exited]
[Thread 0x7fff73fff700 (LWP 27035) exited]
[Thread 0x7fff70985700 (LWP 27043) exited]
[Thread 0x7fff5b7fe700 (LWP 27045) exited]
[Thread 0x7fff71186700 (LWP 27042) exited]
[Thread 0x7fff71ffb700 (LWP 27039) exited]
[Thread 0x7fff737fe700 (LWP 27036) exited]
Program received signal SIGSEGV, Segmentation fault.
0x00007fffffffe10a in ?? ()
(gdb) bt
#0 0x00007fffffffe10a in ?? ()
#1 0x00007ffff79f01dd in ScintillaGTK::StyleIdle (pSci=<optimized out>) at gtk/ScintillaGTK.cxx:2964
#2 0x00007ffff705fd67 in ?? () from /usr/lib/x86_64-linux-gnu/libgdk-x11-2.0.so.0
#3 0x00007ffff50e1fea in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#4 0x00007ffff50e2390 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#5 0x00007ffff50e26b2 in g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#6 0x00007ffff74275b7 in gtk_main () from /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0
#7 0x00007ffff79b46f7 in main_lib (argc=1, argv=0x7fffffffdd38) at libmain.c:1229
#8 0x00007ffff4af7610 in __libc_start_main () from /lib/x86_64-linux-gnu/libc.so.6
#9 0x00000000004006f9 in _start ()
```
This issue is mostly to have the crash reported.
For me this happened on an up2date Debian Testing system at work and on an up2date ArchLinux system at home.
I don't have time to debug this further at the moment but might have a deeper look at it at the weekend. From the fact that the crash seems to happen in Scintilla, it might be related to the recent Scintilla update in master?
---
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/issues/1033
Haskell single line comments consist of at least two dashes "--",
not followed by special symbol.
So in practice everywhere in code you will see a space following "--".
Reference: Haskell 2010 Language Report -> Chapter 2 -> Lexical Structure
You can view, comment on, or merge this pull request online at:
https://github.com/geany/geany/pull/1029
-- Commit Summary --
* Fix Haskell single line comments by adding space
-- File Changes --
M data/filedefs/filetypes.haskell (2)
-- Patch Links --
https://github.com/geany/geany/pull/1029.patchhttps://github.com/geany/geany/pull/1029.diff
---
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/pull/1029
Would it be possible to have an option either in the preferences or in the build menu to execute the lint command periodically ?
---
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/issues/1032
Hi, I seem to have segfaults with geany 1.27 on Linux 4.5.3 with glibc 2.23. They happen very seldom but if they do I can trigger them by editing the same file the crash happend on a certain position. Is this a geany problem or should it be reported somewhere else? I managed to get a very simple backtrace via gdb.
```
[ 4442.960978] geany[1321]: segfault at 0 ip 00007f094992d88e sp 00007fff8e1764f8 error 4 in libc-2.23.so[7f09498a0000+197000
```
```
$ gdb geany
GNU gdb (GDB) 7.11
Copyright (C) 2016 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-pc-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
---Type <return> to continue, or q <return> to quit---
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from geany...(no debugging symbols found)...done.
(gdb) start
Function "main" not defined.
Make breakpoint pending on future shared library load? (y or [n])
Starting program: /usr/bin/geany
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/usr/lib/libthread_db.so.1".
[New Thread 0x7fffeeb96700 (LWP 18778)]
[New Thread 0x7fffee395700 (LWP 18779)]
[New Thread 0x7fffedb94700 (LWP 18780)]
[New Thread 0x7fffed393700 (LWP 18782)]
[Thread 0x7fffedb94700 (LWP 18780) exited]
[New Thread 0x7fffedb94700 (LWP 18783)]
[New Thread 0x7fffde233700 (LWP 18784)]
[New Thread 0x7fffdd056700 (LWP 18785)]
[New Thread 0x7fffdc855700 (LWP 18786)]
[New Thread 0x7fffc7fff700 (LWP 18787)]
[Thread 0x7fffdd056700 (LWP 18785) exited]
[Thread 0x7fffc7fff700 (LWP 18787) exited]
[Thread 0x7fffdc855700 (LWP 18786) exited]
[Thread 0x7fffee395700 (LWP 18779) exited]
[Thread 0x7fffedb94700 (LWP 18783) exited]
[New Thread 0x7fffedb94700 (LWP 18788)]
[Thread 0x7fffedb94700 (LWP 18788) exited]
[New Thread 0x7fffedb94700 (LWP 18803)]
[New Thread 0x7fffc7fff700 (LWP 18804)]
[New Thread 0x7fffdc855700 (LWP 18805)]
[New Thread 0x7fffee395700 (LWP 18806)]
[New Thread 0x7fffdd056700 (LWP 18807)]
[Thread 0x7fffde233700 (LWP 18784) exited]
[Thread 0x7fffc7fff700 (LWP 18804) exited]
[Thread 0x7fffee395700 (LWP 18806) exited]
[Thread 0x7fffdd056700 (LWP 18807) exited]
[Thread 0x7fffdc855700 (LWP 18805) exited]
[New Thread 0x7fffdd056700 (LWP 18808)]
[New Thread 0x7fffdc855700 (LWP 18809)]
[New Thread 0x7fffee395700 (LWP 18810)]
[New Thread 0x7fffc7fff700 (LWP 18811)]
[New Thread 0x7fffde233700 (LWP 18812)]
[New Thread 0x7fffc77fe700 (LWP 18813)]
[New Thread 0x7fffc6ffd700 (LWP 18814)]
[New Thread 0x7fffc67fc700 (LWP 18815)]
[New Thread 0x7fffc5ffb700 (LWP 18816)]
[Thread 0x7fffc67fc700 (LWP 18815) exited]
[Thread 0x7fffc7fff700 (LWP 18811) exited]
[Thread 0x7fffdc855700 (LWP 18809) exited]
[Thread 0x7fffedb94700 (LWP 18803) exited]
[Thread 0x7fffc6ffd700 (LWP 18814) exited]
[Thread 0x7fffc77fe700 (LWP 18813) exited]
[Thread 0x7fffee395700 (LWP 18810) exited]
[Thread 0x7fffdd056700 (LWP 18808) exited]
[Thread 0x7fffde233700 (LWP 18812) exited]
[New Thread 0x7fffde233700 (LWP 18817)]
[Thread 0x7fffde233700 (LWP 18817) exited]
[New Thread 0x7fffde233700 (LWP 18832)]
(geany:18774): Geany-CRITICAL **: sci_get_contents_range: assertion 'start < end' failed
Thread 1 "geany" received signal SIGSEGV, Segmentation fault.
0x00007ffff740f88e in __strcmp_sse2_unaligned () from /usr/lib/libc.so.6
(gdb) backtrace
#0 0x00007ffff740f88e in __strcmp_sse2_unaligned () from /usr/lib/libc.so.6
#1 0x00007fffde4f84e1 in ?? () from /usr/lib/geany/pairtaghighlighter.so
#2 0x00007ffff79a290c in ?? () from /usr/lib/libgeany.so.0
#3 0x00007ffff51cafa5 in g_closure_invoke () from /usr/lib/libgobject-2.0.so.0
#4 0x00007ffff51dcff1 in ?? () from /usr/lib/libgobject-2.0.so.0
#5 0x00007ffff51e5829 in g_signal_emit_valist () from /usr/lib/libgobject-2.0.so.0
#6 0x00007ffff51e6585 in g_signal_emit_by_name () from /usr/lib/libgobject-2.0.so.0
#7 0x00007ffff7994d9f in ?? () from /usr/lib/libgeany.so.0
#8 0x00007ffff51cafa5 in g_closure_invoke () from /usr/lib/libgobject-2.0.so.0
#9 0x00007ffff51dcff1 in ?? () from /usr/lib/libgobject-2.0.so.0
#10 0x00007ffff51e5d8c in g_signal_emit_valist () from /usr/lib/libgobject-2.0.so.0
---Type <return> to continue, or q <return> to quit---
#11 0x00007ffff51e60bf in g_signal_emit () from /usr/lib/libgobject-2.0.so.0
#12 0x00007ffff79f055f in ?? () from /usr/lib/libgeany.so.0
#13 0x00007ffff7a1579b in ?? () from /usr/lib/libgeany.so.0
#14 0x00007ffff7a1cc7a in ?? () from /usr/lib/libgeany.so.0
#15 0x00007ffff79f0065 in ?? () from /usr/lib/libgeany.so.0
#16 0x00007ffff4aeedba in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#17 0x00007ffff4aef160 in ?? () from /usr/lib/libglib-2.0.so.0
#18 0x00007ffff4aef482 in g_main_loop_run () from /usr/lib/libglib-2.0.so.0
#19 0x00007ffff6e6f4e7 in gtk_main () from /usr/lib/libgtk-x11-2.0.so.0
#20 0x00007ffff79b2b07 in main_lib () from /usr/lib/libgeany.so.0
#21 0x00007ffff73a2741 in __libc_start_main () from /usr/lib/libc.so.6
#22 0x00000000004005e9 in ?? ()
```
Sorry if this is geany unrelated.
---
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/issues/1031
The `toggle comments` menu item has a magical operation not hinted at by its name. It does not actually "toggle comments" but in fact comments uncommented lines with its own magic marker (by default "~ ") and will only uncomment lines with its marker. It does *not* by default toggle normal comments.
This can be useful to comment/uncomment sections of code, but without documentation and with a name that does not hint of the possibilities its hard to discover.
Suggestions better than "Magic Toggle Comments" welcome :)
---
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/issues/1027
I up graded to Windows 10 and my Geany was fine.
Now with a new computer and a full install of Windows 10, the execute button doesn't work with Geany 1.22 or 1.27
I reconfigured the Execute action in Build->Set Builds Commands to this:
D:\Comodo\Dragon\dragon.exe %d\%f && exit
Now it executes my HTML but there is an annoying double flash from opening and closing a DOS window.
Any suggestions?
---
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/issues/1028
Haskell single line comments consist of "-- " sequence of characters and not "--". For example, in many cases GHC considers "--" commented lines as not actually commented. Everywhere in code you will see a space following "--".
You can view, comment on, or merge this pull request online at:
https://github.com/geany/geany/pull/1026
-- Commit Summary --
* Fix Haskell single line comments by adding space
-- File Changes --
M data/filedefs/filetypes.haskell (2)
-- Patch Links --
https://github.com/geany/geany/pull/1026.patchhttps://github.com/geany/geany/pull/1026.diff
---
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/pull/1026
Please consider adding a menu item under Document to load the full path name of the current document to the clipboard as this would, I believe, be very useful for driving other software It is possible to obtain this information by using Find Files under Documents or from the Status tab but neither approach is so obvious or convenient Thanks very much!
---
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/issues/846
As for reference:
[wiki.haskell.org Reference card](https://wiki.haskell.org/Reference_card#Comments)
[Beginning Haskell: A Project-Based Approach](https://books.google.ru/books?id=IZsQAwAAQBAJ&pg=PA356&lpg=PA356&dq=haskell+single-line+comment&source=bl&ots=Dqqd8AKZzk&sig=9c5wRDsU9QqAqypIjP1AGSHpI4E&hl=en&sa=X&ved=0ahUKEwiA5O2D1cHMAhUEGZoKHaCVCn4Q6AEIWDAJ#v=onepage&q=haskell%20single-line%20comment&f=false)
---
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/commit/1529e3b327d71bf73e7517ae9c9ade41326ba…