After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 781013 - Terminal from "Run output" and "Build output" are not properly scrolled
Terminal from "Run output" and "Build output" are not properly scrolled
Status: RESOLVED FIXED
Product: gnome-builder
Classification: Other
Component: general
3.23.x
Other Linux
: Normal normal
: ---
Assigned To: GNOME Builder Maintainers
GNOME Builder Maintainers
Depends on:
Blocks: 781010
 
 
Reported: 2017-04-07 08:35 UTC by Carlos Soriano
Modified: 2017-08-13 10:55 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
posible fix or workaround (1.14 KB, patch)
2017-05-08 00:44 UTC, Fernando Fernández 		committed Details | Review

Description Carlos Soriano 2017-04-07 08:35:14 UTC 
Seems there is a miscalculation or race that makes the "Build output" terminal to not be scrolled properly, so the dev cannot follow easily the process.

This is good for newcomers since otherwise is hard to track the errors when building and can be confusing.
Comment 1 Christian Hergert 2017-04-07 09:14:35 UTC 
This is not an easy bug. It is deep in the animation code of gtktextview/gtkadjustment.

Run output does not use textview, but instead VteTerminal, so I'm curious what the behavior you're seeing there is.
Comment 2 Carlos Soriano 2017-04-07 09:17:47 UTC 
right, ignore Run Output.
Comment 3 Fernando Fernández 2017-05-08 00:44:38 UTC 
Created attachment 351317 [details] [review]
posible fix or workaround

This patch try fix this bug by keeping the cursor at the end of the textview buffer.
Comment 4 Christian Hergert 2017-05-08 21:13:00 UTC 
Comment on attachment 351317 [details] [review]
posible fix or workaround

Seems reasonable at least for now.
Comment 5 Nelson Benitez 2017-08-13 10:55:10 UTC 
The patch was committed and fixed the issue, so if you don't mind I'll be closing the bug. Regards.