Misconception of core.move and core.go key bindings

[rafo]

As far as I can see and if I don't miss any functions, I have the feeling that there are some unlogical behavior to moving the cursor with core.move and core.go:

1. "H" "core.move.left Should move the cursor to the parent directory and not to the top of the current directory. See also (3).
2. "L" "core.move.right" Should move the cursor to the subdirectory (if a folder is under the cursor) and not to the end of the list. core.open does the job for me, but there might be users to have a separate key for open files and open folders.
3. You already have core.move.end which brings the cursor to the end of the list (and which is semantically correct). Where is something like core.move.start or core.move.top to bring the cursor to the top if (1) is corrected?
4. Movement in left and right directions in different display modes are still possible with the left and right keys. Maybe some users will need dedicated bindings with something like core.go.leftand core.go.right...