Bug 488238 - Moving the blue selection with the up and down arrows
Summary: Moving the blue selection with the up and down arrows
Status: RESOLVED UNMAINTAINED
Alias: None
Product: krusader
Classification: Applications
Component: general (show other bugs)
Version: 2.8.1
Platform: Other Linux
: NOR wishlist
Target Milestone: ---
Assignee: Krusader Bugs Distribution List
URL:
Keywords:
: 487988 (view as bug list)
Depends on:
Blocks:
 
Reported: 2024-06-09 04:24 UTC by Mikhail
Modified: 2024-10-15 06:59 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Mikhail 2024-06-09 04:24:59 UTC 
What you should get:
Add an item setting in selection mode to enable moving the blue selection with the up and down arrows.
With the selection item enabled to move the selection with the arrows, the blue selection is moved.
This is very convenient when using only the keyboard, and not only in this case.
PS. This is the same selection that happens when you select with the left mouse button or Shift/Ctrl + left mouse. Not the selection that is dotted style!
Comment 1 Alex Bikadorov 2024-07-03 11:05:49 UTC 
I don't understand. You can use SHIFT+Up/Down keys to change the (blue) selection.
Comment 2 Mikhail 2024-07-03 11:16:35 UTC 
(In reply to Alex Bikadorov from comment #1)
> I don't understand. You can use SHIFT+Up/Down keys to change the (blue)
> selection.

This is not what me need. In Total Commander it is implemented as it should be.
Comment 3 Alex Bikadorov 2024-07-03 12:27:19 UTC 
I don't know about Total Commander but in Double Commander the behavior is the same as in Krusader - it only looks different.

Maybe having CTRL+Up/Down could change the (blue) selection to the current (dotted) cursor selection, so that only one item is  (blue) selected. That would be a valid improvement in my opinion.
Comment 4 Alex Bikadorov 2024-07-15 14:10:42 UTC 
*** Bug 487988 has been marked as a duplicate of this bug. ***