https://bugs.kde.org/show_bug.cgi?id=494125
--- Comment #59 from kaminata <[email protected]> --- (In reply to Nate Graham from comment #55) > I have a fairly organization-heavy workflow for my business's record-keeping > system. Of course I use Dolphin and other KDE software for this! I find > myself quite commonly opening a file to verify its contents, immediately > closing it, and then renaming, cutting, or deleting the file. Sometimes I > use the pointer for opening files, and sometimes the keyboard. But I always > use the keyboard for the above file manipulation actions (because it's > fast!). > > When I use the keyboard to open a file for the above workflow, the file > remains selected afterwards and I can target it with the keyboard shortcuts > for file manipulation actions. This is fine. > > But when I use the pointer to open a file, it gets de-selected afterwards, > so using the keyboard shortcut for any of the above actions does not target > the file, but rather enters selection mode. This is really annoying, as then > I have to exit selection mode to recover from my error, select the file > somehow, and then press the keyboard shortcut again. This actually > introduces the possibility of new errors. > > I've tried to get used to the behavior change introduced by > https://invent.kde.org/system/dolphin/-/commit/ > 122fee5625f0285ec4ebda79162c72390989eb2a for a year, but I just can't. > > Yes, I know I can press Shift+Enter to select the file, but: > 1. Because it isn't always required, there's extra cognitive overhead to > remember if I have to or not, especially when rapidly switching between > mouse and keyboard workflows. > 2. It's an extra step that slows me down. > 3. It isn't a general solution for everyone annoyed by this because it's > un-discoverable. I only know it because Felix (one of the Dolphin > maintainers) mentioned it to me. > > I totally get the safety desire behind the change to not select files after > opening them, but after a year of people complaining, I think it's time to > consider the experiment a failure. The bug report is still open, so I assume > reverting this change hasn't been vetoed. Congrats! We've talking about this for a year. And thank you for being sane! -- You are receiving this mail because: You are watching all bug changes.
