F6 key press is quite confusing
This bug report was converted into a question: question #113312: F6 key press is quite confusing.
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| byobu (Ubuntu) |
Invalid
|
Low
|
Unassigned | ||
Bug Description
Binary package hint: byobu
In alsamixer F6 is for switching soundcards so I was quite confused to have byobu quit on me. I think alsamixer is something a user of byobu would likely use so maybe F6 shouldn't have a keybinding.
ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: byobu 2.68-0ubuntu1
ProcVersionSign
Uname: Linux 2.6.32-22-generic x86_64
Architecture: amd64
CheckboxSubmission: fee5e196cb921cb
CheckboxSystem: 2a6f54df59af338
Date: Wed Jun 2 10:12:54 2010
PackageArchitec
ProcEnviron:
PATH=(custom, user)
LANG=en_US.UTF-8
SHELL=/bin/zsh
SourcePackage: byobu
| Brian Murray (brian-murray) wrote | #1 |
| Dustin Kirkland (kirkland) wrote | #2 |
| Changed in byobu (Ubuntu): | |
| importance: | Undecided → Low |
| status: | New → Invalid |
Hey Brian-
That's a tough one ...
We tried to bind all of the F-keys in Byobu that weren't already taken in gnome-terminal and konsole. This basically excluded byobu from using:
# F1 | 'help' in gnome-terminal
# F10 | 'toolbar' in gnome-terminal
# F11 | 'fullscreen' in gnome-terminal
However, I respect your question, and these comes up from time to time. Two programs which are often used inside of byobu on a command line that also make liberal use of the f-keys are htop and mc. I suppose I will be adding alsamixer to that list. The commonly understood workaround is to temporarily disable your F-key bindings while you're using alsamixer/htop/mc, and then re-enable them when you're done. You can easily toggle the f-key bindings on and off with ctrl-a-! (where ctrl-a is your chosen escape sequence).
See also Bug #589016, where I just added a visual queue to this toggle, which will switch the Menu:<F9> to and from Menu:<^a-@> when you toggle.
Hope that helps. I think that's about the best I can do with this bug. I'll probably need to mark this won't-fix or convert to a question.