Re: [Github-comments] [geany/geany] document location moves to cursor location on save (#1590)

[Quentin Glidic]

Oh, and please try to reproduce with Weston (at least 1.12).

-- 
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/1590#issuecomment-325917836

Re: [Github-comments] [geany/geany] document location moves to cursor location on save (#1590)

[Evgeni Golov]

Fedora 26 here, running Wayland, and I can't reproduce the issue.

* Geany 1.31
* GTK 3.22.19
* GLib 2.52.3

Opening a long file, doing some changes here and there. Pressing ^s. Neither my 
cursor nor the scrolling moves anywhere.

-- 
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/1590#issuecomment-325905012

Re: [Github-comments] [geany/geany] document location moves to cursor location on save (#1590)

[Quentin Glidic]

Could you both run `WAYLAND_DEBUG=debug geany` and pastebin the output please? 
Make it as quick as possible because it’ll be quite verbose. And shut Geany 
down right after you save.

-- 
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/1590#issuecomment-325917309

Re: [Github-comments] [geany/geany] document location moves to cursor location on save (#1590)

[Evgeni Golov]

For me it was `WAYLAND_DEBUG=1` that triggered the behavior you wanted.

[geany.txt](https://github.com/geany/geany/files/1262860/geany.txt)

-- 
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/1590#issuecomment-325922074

Re: [Github-comments] [geany/geany] “Join lines” doesn’t work if long line marker is disabled (#1591)

[elextr]

Yeah, gets the column but only uses it to [test if it 
exists](https://github.com/geany/geany/blob/0dc1e4c6d3129135b768f20b848c653e84c135ee/src/keybindings.c#L2429)
 and doesn't use it again.  Looks like its a copy of `reflow_paragraph` above.

Also that should go in the menu, its not very discoverable just in the 
keybindings, but that needs someone with the right version of Glade to edit.

-- 
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/1591#issuecomment-325954676

Re: [Github-comments] [geany/geany] document location moves to cursor location on save (#1590)

[ITwrx]

i can't replicate this issue on my laptop which is a largely identical setup 
with either geany or geany-gtk3. these packages are the same on either laptop 
or desktop. 

glib2 2.52.3-1
gnome-shell 3.24.3-1
gtk2 2.24.31-1
gtk3 3.22.19-2
wayland 1.14.0-1
wayland-protocols 1.10-1

On desktop both geany and geany-gtk3 exhibit the reported behavior. pls see 
geany-wayland-debug from desktop machine: https://pastebin.com/70p3UmWw
thanks

-- 
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/1590#issuecomment-326148512

Re: [Github-comments] [geany/geany] Fix 1069 (#1445)

[Thomas Martitz]

@elextr @b4n @codebrainz ping

-- 
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/1445#issuecomment-326124722

Re: [Github-comments] [geany/geany] Is there an easy way to increase line spacing? (#1592)

[paul1149]

Awesome. That was easy. Thanks so much!

-- 
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/1592#issuecomment-326005558

Re: [Github-comments] [geany/geany] Is there an easy way to increase line spacing? (#1592)

[paul1149]

Closed #1592.

-- 
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/1592#event-1227712152

Re: [Github-comments] [geany/geany] crash on multiline regexp (#1586)

[elextr]

> I attach the output of strace (last part) and ltrace (last lines of the file) 
> after the crash. Can that help?I also verified that the crash is not due to a 
> particular pattern in the input file between lines 5500 (where it doesn't 
> crash) and 5600 (where it crashes). Apparently, only size matters.

Actually you didn't attach it or github ignored the attachments, but that 
probably won't help so don't waste time trying another way, just follow the 
instructions to run gdb and get the backtrace:

```
gdb geany
```
at the `(gdb)` prompt:
```
run -v
```
do whatever crashes it and after it crashes and returns to the gdb prompt:
```
bt
```
and return while it says `return to continue`

Paste the output.


-- 
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/1586#issuecomment-325988567

Re: [Github-comments] [geany/geany] Is there an easy way to increase line spacing? (#1592)

[elextr]

`filetypes.common` has a `line_height` setting that sets extraascent and 
extradescent.

-- 
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/1592#issuecomment-326003757

[Github-comments] [geany/geany] Is there an easy way to increase line spacing? (#1592)

[paul1149]

I edit large text files in geany, and the wall of text is tiring on the eyes. A 
bit of white space would help tremendously. I've come across the Scintilla 
command, sci_setextradescent, but have no idea how to implement it. I wonder if 
there's an easy way to achieve this.

Thanks.

-- 
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/1592

Re: [Github-comments] [geany/geany] crash on multiline regexp (#1586)

[Chayyoo]

Here's the end of it:#16362 0x712a751c in ?? () from 
/lib/x86_64-linux-gnu/libpcre.so.3
#16363 0x712b15f0 in ?? () from /lib/x86_64-linux-gnu/libpcre.so.3
#16364 0x712a751c in ?? () from /lib/x86_64-linux-gnu/libpcre.so.3
#16365 0x712b6903 in pcre_exec () from 
/lib/x86_64-linux-gnu/libpcre.so.3
#16366 0x753fc32b in g_match_info_next () from 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#16367 0x753fdbcf in g_regex_match_full () from 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#16368 0x779b2f97 in find_regex (sci=sci@entry=0xa68400, 
pos=pos@entry=0, regex=regex@entry=0xa87920, multiline=multiline@entry=16, 
match=match@entry=0xda9f40) at search.c:1944
#16369 0x779b6f84 in search_find_next (sci=0xa68400, 
str=str@entry=0xdac470 "^(\\d+?);(\\d+?);(\\d+?);[BCST]+\\n(.*?\\n)*\\1", 
flags=flags@entry=(GEANY_FIND_REGEXP | GEANY_FIND_MULTILINE), 
    match_=match_@entry=0x0) at search.c:2044
#16370 0x7797b17e in document_find_text (doc=doc@entry=0xbb5560, 
text=text@entry=0xdac470 "^(\\d+?);(\\d+?);(\\d+?);[BCST]+\\n(.*?\\n)*\\1", 
    original_text=original_text@entry=0xda6660 
"^(\\d+?);(\\d+?);(\\d+?);[BCST]+\\n(.*?\\n)*\\1", 
flags=flags@entry=(GEANY_FIND_REGEXP | GEANY_FIND_MULTILINE), 
search_backwards=search_backwards@entry=0, 
    match_=match_@entry=0x0, scroll=1, parent=0x73b9b0) at document.c:2345
#16371 0x779b33e0 in on_replace_dialog_response (dialog=0x73b9b0, 
response=1, user_data=) at search.c:1509
#16372 0x758c7518 in g_cclosure_marshal_VOID__ENUMv () from 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#16373 0x758c51d4 in ?? () from 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#16374 0x758df9a6 in g_signal_emit_valist () from 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#16375 0x758e008f in g_signal_emit () from 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#16376 0x758c51d4 in ?? () from 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
---Type  to continue, or q  to quit---
#16377 0x758df9a6 in g_signal_emit_valist () from 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#16378 0x758e008f in g_signal_emit () from 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#16379 0x76d85f35 in ?? () from 
/usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0
#16380 0x758c4fa5 in g_closure_invoke () from 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#16381 0x758d6afc in ?? () from 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#16382 0x758dfd5c in g_signal_emit_valist () from 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#16383 0x758e008f in g_signal_emit () from 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#16384 0x76d84e79 in ?? () from 
/usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0
#16385 0x76e2baec in ?? () from 
/usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0
#16386 0x758c4fa5 in g_closure_invoke () from 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#16387 0x758d756e in ?? () from 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#16388 0x758df7f9 in g_signal_emit_valist () from 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#16389 0x758e008f in g_signal_emit () from 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#16390 0x76f4393c in ?? () from 
/usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0
#16391 0x76e2a284 in gtk_propagate_event () from 
/usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0
#16392 0x76e2a63b in gtk_main_do_event () from 
/usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0
#16393 0x76a9ec8c in ?? () from 
/usr/lib/x86_64-linux-gnu/libgdk-x11-2.0.so.0
#16394 0x753ea197 in g_main_context_dispatch () from 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#16395 0x753ea3f0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#16396 0x753ea712 in g_main_loop_run () from 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#16397 0x76e29697 in gtk_main () from 
/usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0
#16398 0x7799f527 in main_lib (argc=1, argv=0x7fffdf68) at 
libmain.c:1233
#16399 0x77364830 in __libc_start_main (main=0x4005a0 , argc=2, 
argv=0x7fffdf68, init=, fini=, 
rtld_fini=, stack_end=0x7fffdf58)
    at ../csu/libc-start.c:291
#16400 0x004005d9 in _start ()
Will that do?
 

On Wednesday, 30 August 2017, 15:23, elextr  
wrote:
 

 
I attach the output of strace (last part) and ltrace (last lines of the file) 
after the crash. Can that help?I also verified that the crash is not due to a 
particular pattern in the input file between lines 5500 (where it doesn't 
crash) and 5600 (where it crashes). Apparently, only size matters.
Actually you didn't attach it or github ignored the attachments, but that 
probably won't help so don't waste time trying another way, just follow the 
instructions to run gdb and get the backtrace:gdb geany
at the (gdb) prompt:run -v
do whatever crashes it and 

Re: [Github-comments] [geany/geany] crash on multiline regexp (#1586)

[elextr]

Ok, that shows that the crash is inside the PCRE library that Glib uses for 
regular expression handling.  But what is the actual crash? Is it a 
segmentation violation?  If it depends on size, are you running out of memory?

-- 
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/1586#issuecomment-326002297

Re: [Github-comments] [geany/geany] crash on multiline regexp (#1586)

[Chayyoo]

It's a segmentation fault ("core dumped"). How can I tell if that's an out of 
memory?
 

On Wednesday, 30 August 2017, 16:10, elextr  
wrote:
 

 Ok, that shows that the crash is inside the PCRE library that Glib uses for 
regular expression handling. But what is the actual crash? Is it a segmentation 
violation? If it depends on size, are you running out of memory?—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.  

   

-- 
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/1586#issuecomment-326003637

Re: [Github-comments] [geany/geany] crash on multiline regexp (#1586)

[Chayyoo]

I attach the output of strace (last part) and ltrace (last lines of the file) 
after the crash. Can that help?I also verified that the crash is not due to a 
particular pattern in the input file between lines 5500 (where it doesn't 
crash) and 5600 (where it crashes). Apparently, only size matters.
 

On Tuesday, 29 August 2017, 9:32, Kris Van Bruwaene  
wrote:
 

 When I run "gdb geany" Geany doesn't seem to start (no window). Gdb just 
says:Reading symbols from geany...done.
(gdb) 
and it stays that way no matter how many returns I pressI also tried to 
start Geany the regular way and then couple gdb to the process number with gdb 
-p 14825, but then the Geany screen becomes blank.As I said, I'm totally 
unfamiliar with gdb.
 

On Tuesday, 29 August 2017, 2:21, elextr  wrote:
 

 Note that you may need to keep pressing return to get the whole backtrace.—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.  

   

   

-- 
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/1586#issuecomment-325972318

[Github-comments] [geany/geany] geany cannot restore previous window size (after maximized) (#1593)

[llpub]

How to reproduce:
(geany1.24 - 1.30, with gtk2 from xfce4.14, gnome3.14)

1. make sure "Save window position and geometry" is checked in preference;
2. resize geany window to any size (except nearly maximized size), here call 
this size as sizeA;
3. maximize geany window;
4. close && open geany, geany window would be nearly maximized size.

Here geany window should be sizeA. It seems that geany lost sizeA info after 
maximized. Same problems can be observed in some gtk2 softwares (e.g. sublime 
text). However, some other gtk2 apps can restore window size even after 
maximized (e.g. firefox gtk2 version).
Thanks in advance.


-- 
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/1593

[Github-comments] [geany/geany] Verbose symbols for functions (#1594)

[OMG Eto Zhe BFG]

I'd like to suggest a feature.

Currently symbols list is very brief, it would be nice to know more about 
functions in it: for example, return type and input arguments, probably length 
in LOC.

-- 
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/1594

Re: [Github-comments] [geany/geany] Verbose symbols for functions (#1594)

[elextr]

The functions declaration is shown by the tooltip when you hold the cursor over 
the entry on the symbols pane.

-- 
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/1594#issuecomment-326184612

Re: [Github-comments] [geany/geany] geany cannot restore previous window size (reopen after maximized) (#1593)

[llpub]

Closed #1593.

-- 
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/1593#event-1228785731

Re: [Github-comments] [geany/geany] geany cannot restore previous window size (reopen after maximized) (#1593)

[llpub]

Thank you, now I understand this.

-- 
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/1593#issuecomment-326179387