Suggestion to change F10 Confirm key in wicr-curses to something that doesn't conflict with standard terminal key bindings.

Bug #1159323 reported by Jeff Johnson on 2013-03-24
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
wicd
Medium
Tom Van Braeckel

Bug Description

Suggestion to change F10 Confirm key in wicr-curses to something that doesn't conflict with standard terminal key bindings.

Most linux terminals seem to bind F10 to the File menu, which makes using wicr-curses difficult. It seems to me that the most common usage of wicr-curses is via an ssh session in a terminal, which probably already binds F10. With very limited testing, F5, F6, F7, F8 seem like they would work.

Related branches

sandwood (keysandwood) wrote :

I have the same "issue".
Instead of using one of the Fx key (which are likely to have been user-configured) ,I suggest to use the upper S and to rename the "OK" by "SAVE".

Fixed. I took up your suggestion to use S for Save, and kept the F10 support just in case some users are accustomed to it.

Changed in wicd:
status: New → Fix Committed
importance: Undecided → Medium
assignee: nobody → Tom Van Braeckel (tomvanbraeckel)
milestone: none → 1.7.5
Changed in wicd:
milestone: 1.7.5 → 1.7.3
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers