don't always consume {next,prev}_tab signals
Bug #568287 reported by
Chris Jones
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Terminator |
Incomplete
|
Wishlist
|
Unassigned | ||
Bug Description
When there are no tabs, we should emit whatever keybinding is mapped to next_tab/prev_tab to the underlying terminal.
An argument against doing this would be that it introduces inconsistency in the meaning of Ctrl-PageUp/Down. Having said that, in the current default setup, a user expecting Ctrl-PageUp to be delivered to something running inside the Terminal will get no visual feedback why nothing happened if there are no tabs present.
| Changed in terminator: | |
| status: | New → Incomplete |
| importance: | Undecided → Wishlist |
To post a comment you must log in.
