[dolphin] [Bug 523885] Dolphin shouldn't keep user-selected 'Copy To' and 'Move To' locations that are no longer available

Méven Car <[email protected]>
Newsgroups gmane.comp.kde.devel.bugs
Message-ID <[email protected]/>
https://bugs.kde.org/show_bug.cgi?id=523885

Méven Car <[email protected]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|REPORTED                    |CONFIRMED
     Ever confirmed|0                           |1
                 CC|                            |[email protected]

--- Comment #1 from Méven Car <[email protected]> ---
> Firstly, locations selected by users in either temporarily mounted disk partitions or various removable (e.g. USB) media etc. usually become unwanted leftovers in the list there.

The filesystem for those paths would need to be first check if they are network
mounts, as they could be unresponsive, and freeze dolphin.
In case of ENOENT then remove indeed.

> Secondly, this list can become overcrowded in time when users select many different location via 'Browse...' 

We might limit the number of entries in the menu at 5 or 10. I'd go with 5.

> Dolphin should perhaps check availability of the locations listed under the headings '[kuick-copy]' and '[kuick-move]' in `~/.config/dolphinrc` maybe every time it starts, if not periodically, to clear those locations that are no longer available.

Or every  time the copy-to/move-to menu is constructed, so none-users of those
won't pay the consequences.

> There might also be an option to edit the list in the sub-menu of  'Copy To' and 'Move To' commands, enabling users to remove, add and perhaps even pin items.

I would consider that another bug, that would increase the menu "power" for
advanced users.
~/.config/dolphinrc is already editable.
Instead of pinning, I would consider adding panel places that aren't directly
in $HOME, or bookmarks, in another submenu.

-- 
You are receiving this mail because:
You are watching all bug changes.
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.