Bug 1305062 - mouse no longer works with info
Summary: mouse no longer works with info
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: texinfo
Version: 23
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Vitezslav Crhonek
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-02-05 13:53 UTC by H.J. Lu
Modified: 2016-02-12 11:51 UTC (History)
2 users (show)

Fixed In Version: texinfo-6.0-2.fc23
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-02-12 11:51:26 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description H.J. Lu 2016-02-05 13:53:19 UTC
When I do

# info gcc

I can no longer use mouse to copy/paste inside info with texinfo-6.0-1.fc23.

Comment 1 Vitezslav Crhonek 2016-02-09 09:19:15 UTC
Hello,

Info is in "pointer mode" by default since 6.0 release (it allows to use mouse wheel for scrolling).

You can still select text with mouse, you just have to hold Shift concurrently.

However, I'll turn it off (upstream also did), it confuses users... Until the update is released, please use the "workaround" mentioned above.

Comment 2 Fedora Update System 2016-02-09 09:54:15 UTC
texinfo-6.0-2.fc23 has been submitted as an update to Fedora 23. https://bodhi.fedoraproject.org/updates/FEDORA-2016-c202294c99

Comment 3 Fedora Update System 2016-02-10 18:52:04 UTC
texinfo-6.0-2.fc23 has been pushed to the Fedora 23 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2016-c202294c99

Comment 4 Fedora Update System 2016-02-12 11:51:24 UTC
texinfo-6.0-2.fc23 has been pushed to the Fedora 23 stable repository. If problems still persist, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.