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 687118 - add API to disable input (read-only terminal)
add API to disable input (read-only terminal)
Status: RESOLVED FIXED
Product: vte
Classification: Core
Component: general
unspecified
Other All
: Normal enhancement
: ---
Assigned To: VTE Maintainers
VTE Maintainers
Depends on:
Blocks: 626747
 
 
Reported: 2012-10-29 14:30 UTC by Allison Karlitskaya (desrt)
Modified: 2014-04-18 09:48 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Allison Karlitskaya (desrt) 2012-10-29 14:30:29 UTC 
vte is used as a base widget for writing terminal emulator programs but it sees use in other places -- OS installation and upgrade programs come to mind.

The user (who did not launch any program called "terminal") is presented with a vte widget in this context and might think that they could use ^C to copy text.  Of course, this ends up sending a SIGINT instead.

We could add an API to revert ^C to its more common use in cases where vte is being used in these 'embedded' situations.
Comment 1 Christian Persch 2012-10-30 17:20:44 UTC 
You mean something like the embedded terminal showing dpkg output in synaptic?

If there is input expected in these terminals, could use stty to disable ^C causing SIGINT. If there isn't input expected, a 'read-only' view would be a solution.
Comment 2 Allison Karlitskaya (desrt) 2013-01-14 17:57:40 UTC 
Yes.  I mean exactly that.

Input is not expected.  It's meant to be read-only.  Most of the time it's hidden behind an expander, indeed...