Bug 1096791

Summary:	Shift+Down does not open new tab
Product:	[Fedora] Fedora	Reporter:	Alois Mahdal <amahdal>
Component:	rxvt-unicode	Assignee:	Nobody's working on this, feel free to take it <nobody>
Status:	CLOSED ERRATA	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	20	CC:	andreas.bierfert, lnie, mlichvar
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	rxvt-unicode-9.20-2.fc19	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2014-06-05 04:23:04 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Alois Mahdal 2014-05-12 12:38:36 UTC

Description of problem:
When I open new urxvt window with `tabbed` Perl extension and press Shift+Down, nothing happens.   On Debian, for example, this opens new tab.

Version-Release number of selected component (if applicable):
rxvt-unicode-9.19-1.fc20.x86_64

How reproducible:
Always

Steps to Reproduce:
1. `urxvt -pe tabbed`
2. press Shift+Down

Actual results:
No visible change

Expected results:
New tab should be created

Additional info:

In 9.10-2 (626923a), support for Ctrl+T to open tab was added ... I wonder if this is related...?

Comment 1 Alois Mahdal 2014-05-12 14:15:13 UTC

(In reply to Alois Mahdal from comment #0)
> Actual results:
> No visible change

Actually, now I see that this actually does something, it scrolls one line down.

Short history: this is effect of "RFE" bug 510944 which among others, enabled Shift+Up and Shift+Down to scroll one line, which broke `tabbed` extension.  The problem has been addressed by maintainer in commit e4d0a0c but consequentially reverted by bug 667980.

So, sadly, current state is: broken.

Comment 2 Jamie Nguyen 2014-05-13 18:39:36 UTC

Thanks for the report!

I don't know why these Fedora-specific patches were implemented. Any custom key bindings like this can surely be done by the user in ~/.Xresources file or similar. I don't see any reason in this situation to diverge from upstream defaults and surprise our users.

Fixed in all branches. Currently building and updates to follow.

Comment 3 Fedora Update System 2014-05-13 18:55:36 UTC

rxvt-unicode-9.20-2.fc20 has been submitted as an update for Fedora 20.
https://admin.fedoraproject.org/updates/rxvt-unicode-9.20-2.fc20

Comment 4 Fedora Update System 2014-05-13 18:56:05 UTC

rxvt-unicode-9.20-2.fc19 has been submitted as an update for Fedora 19.
https://admin.fedoraproject.org/updates/rxvt-unicode-9.20-2.fc19

Comment 5 Jamie Nguyen 2014-05-13 19:16:02 UTC

(Waiting for security update on EL6 to hit stable before pushing the EL6 build to epel-testing.)

Comment 6 lnie 2014-05-14 03:25:34 UTC

rxvt-unicode-9.20-2.fc19 works

Comment 7 Fedora Update System 2014-05-14 23:52:53 UTC

Package rxvt-unicode-9.20-2.fc20:
* should fix your issue,
* was pushed to the Fedora 20 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing rxvt-unicode-9.20-2.fc20'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2014-6341/rxvt-unicode-9.20-2.fc20
then log in and leave karma (feedback).

Comment 8 Fedora Update System 2014-06-05 04:23:04 UTC

rxvt-unicode-9.20-2.fc20 has been pushed to the Fedora 20 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 9 Fedora Update System 2014-06-27 02:26:42 UTC

rxvt-unicode-9.20-2.fc19 has been pushed to the Fedora 19 stable repository.  If problems still persist, please make note of it in this bug report.