Re: [orca-list] Orca Hangs When Trying to Read Large Text File in Pluma
- From: Volodymyr Dorozhinsky <dorozhinsky ukr net>
- To: Jude DaShiell <jdashiel panix com>, Arkadiusz Kozioł <zywek-mailing nvps pl>, orca-list gnome org
- Subject: Re: [orca-list] Orca Hangs When Trying to Read Large Text File in Pluma
- Date: Sat, 14 Mar 2020 20:17:08 +0100
Hi,
"Was plume even designed to edit large files?"
(VD) It seems it was. Since navigation through the file and its editing works fine. The only issue is with
screen reader speaks file content.
"If not, other options
exist. Genie gets good ratings and emacs can get a job like that done
even xemacs could do that."
(VD) Moreover even nano can do that... But my question is about
graphical editors.
Best Regards
Volodymyr
On 3/14/20 7:33 PM, Jude DaShiell wrote:
Was plume even designed to edit large files? If not, other options
exist. Genie gets good ratings and emacs can get a job like that done
even xemacs could do that.
On Sat, 14 Mar 2020, Arkadiusz Kozio? wrote:
Date: Sat, 14 Mar 2020 13:56:32
From: Arkadiusz Kozio? <zywek-mailing nvps pl>
To: orca-list gnome org
Subject: Re: [orca-list] Orca Hangs When Trying to Read Large Text File in
Pluma
So you can't do anything with this at-spi2 events?
W dniu 14.03.2020 o?18:35, Joanmarie Diggs pisze:
Not 100% sure. Gtk (I assume) is being super spammy, not just with
text-insertion events (1 event for every 8192 characters inserted), but also
with caret-moved events because Gtk (I assume) is emitting a caret-moved
event after each insertion.
But it looks like it might be an AT-SPI2 one as well. Because at some point
in the flood, we go from getting valid events to getting events from "dead"
accessibles. For instance:
13:20:39.753794 - EVENT MANAGER: object:text-changed:insert for [DEAD] in
[DEAD] (10764288, 8192,
8wekyb3d8bbwe/AppCS/Assets/ModularMusic/Classic_00/music_Neutral_01_LOOP_E.wma:
OK
13:20:39.753950 - EVENT MANAGER: object:text-caret-moved for [DEAD] in
[DEAD] (10772480, 0, 0)
13:20:39.754068 - EVENT MANAGER: object:property-change:accessible-value for
[DEAD] in [DEAD] (0, 0, 0)
That suggest that Pluma may have gone completely non-responsive (as far as
AT-SPI2 is concerned) and/or that AT-SPI2 is completely unhappy. Not sure
which, but that's not an Orca bug. All I can do in Orca is try to discard
these events as quickly as possible.
On 3/14/20 13:12, Alex ARNAUD via orca-list wrote:
Le 14/03/2020 ? 18:06, Joanmarie Diggs a ?crit?:
Confirmed. Orca is getting flooded by insanely large text insertion
events. I'll see if I catch that condition and eliminate it. Thanks for
the report!
Is it a GTK issue or a more general one?
Best regards.
_______________________________________________
orca-list mailing list
orca-list gnome org
https://mail.gnome.org/mailman/listinfo/orca-list
Orca wiki: https://wiki.gnome.org/Projects/Orca
Orca documentation: https://help.gnome.org/users/orca/stable/
GNOME Universal Access guide:
https://help.gnome.org/users/gnome-help/stable/a11y.html
_______________________________________________
orca-list mailing list
orca-list gnome org
https://mail.gnome.org/mailman/listinfo/orca-list
Orca wiki: https://wiki.gnome.org/Projects/Orca
Orca documentation: https://help.gnome.org/users/orca/stable/
GNOME Universal Access guide:
https://help.gnome.org/users/gnome-help/stable/a11y.html
_______________________________________________
orca-list mailing list
orca-list gnome org
https://mail.gnome.org/mailman/listinfo/orca-list
Orca wiki: https://wiki.gnome.org/Projects/Orca
Orca documentation: https://help.gnome.org/users/orca/stable/
GNOME Universal Access guide:
https://help.gnome.org/users/gnome-help/stable/a11y.html
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]