bug: Improve navigation when default keybindings block j/k

[StefanBethge]

Problem:
You cannot use j/k for navigation because they are intercepted by the default key mapping.

Suggested solution:
Use Tab to switch focus instead: first move to the search field, then press Tab again to move to the results list.

[seletz]

@StefanBethge why is this a problem? The configuration allows to rebind actions to any key?

[StefanBethge]

@seletz in My opinion is, a default Binding should Not have These issue. When rebinding a Key. I think its okay. But I need some minutes to understand what happend, While I search a task.

[seletz]

@StefanBethge OK I See. So the real issue is too create and document (readme) sane default key bindings. I agree.

These are the key maps I use:

[keys]
  cursor_down = ["down", "j"]
  cursor_up = ["up", "k"]
  detail_add = ["a"]
  detail_delete = ["d"]
  detail_edit = ["e"]
  global_back = ["esc"]
  global_help = ["?"]
  global_next_week = ["n"]
  global_prev_week = ["p"]
  global_quit = ["q", "ctrl+c"]
  global_refresh = ["r"]
  grid_enter = ["enter"]
  grid_next_col = ["right", "l"]
  grid_prev_col = ["left", "h"]
  grid_search = ["/"]
  search_toggle = ["ctrl+a"]

Could you please rephrase the Issue and maybe come up with a more suitable key binding? Notice I count "n,p" for next and previous week instead left, right, Which I found very annoying. 🤷‍♂️

[StefanBethge]

@seletz This only happens in the search grid. When I disable j/k for up/down navigation, everything works fine.
The question is whether a default key binding should prevent users from typing j or k in a search field.
When the default binding is changed to the arrow keys, the issue is gone.
Keys shouldn’t be rebound by default if that interferes with normal typing.

At the moment, every user has to change the default key binding manually for search to work properly.