Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 209403 - app-misc/screen standard binding for "-" (blank window) is changed in Gentoo's config
Summary: app-misc/screen standard binding for "-" (blank window) is changed in Gentoo'...
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: New packages (show other bugs)
Hardware: All Linux
: High trivial (vote)
Assignee: Sven Wegener
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-02-08 22:24 UTC by Mike Nerone
Modified: 2015-10-10 16:31 UTC (History)
1 user (show)

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Mike Nerone 2008-02-08 22:24:57 UTC
This is a minor request, but I thought I'd throw it out there. In screen's default configuration, the "-" key (i.e. ^A followed by "-") is bound to "select -", meaning to switch to a blank window. Many experienced users of screen make use of this capability (e.g. I frequently blank the window during compiles I'm not watching actively in order to save both a bit of bandwidth and some SSH encryption overhead).

The ebuild for screen in the tree has an /etc/screenrc that overrides the above default behavior that experienced users expect, instead binding "-" to "resize -3" (shrink the current window a bit). I agree that that's a useful binding, as well, but I think it would be best to choose an alternate key (perhaps "_"? It's still next to the "+" and the user could then hold shift for both enlarging and reducing).

Thanks for considering it.
Comment 1 Pacho Ramos gentoo-dev 2012-12-15 13:26:28 UTC
Still valid with latest screen version in the tree?
Comment 2 Mike Nerone 2012-12-30 02:14:48 UTC
Actually, I dunno. :) I switched to tmux long ago (far superior for any searchers that find this bug). I no longer care about this bug. Feel free to do with it what you will.
Comment 3 Patrice Clement gentoo-dev 2015-10-10 16:31:25 UTC
Closing this bug as per previous comment.