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
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
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
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:
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
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
@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
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
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
> 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
`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
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
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
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.
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
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
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,
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
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:
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
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
21 matches
Mail list logo