But you can be sure people would whine.  If someone changes their settings in KDE, they might not expect the Delete button in amaroK to change its behaviour.  I think amaroK's different enough from Konqueror for it to be more intuitive to give it its own Trash settings.

I don't think the OP made himself terribly clear ... it isn't that he was confusing the difference between "remove from playlist" and "delete file", it was that when you choose to delete a playlist from the "Playlists" section, it deletes all of the songs that this playlist points to.  The last post on this page makes it a little more clear:
http://forums.gentoo.org/viewtopic-t-378955-highlight-amarok+delete+playlist.html
There are lots of times that I want to remove a specific playlist file itself and not each and every song it points to.

Can anyone confirm that this was a bug that got fixed?  I don't feel like making dummy playlists and copying files so that if they get deleted it won't damage my real music.

In 1.4.1 (to be released) we've changed the behaviour slightly: now the data is moved to Trash by default.

Mark Kretschmann wrote:In 1.4.1 (to be released) we've changed the behaviour slightly: now the data is moved to Trash by default.

and what is the behaviour, if the trash doesn't contain enough space?
a) i will get a warning like "action aborted - not enough space left on device"?
b) anything that doesnt fit in the trash will be deleted silently?

oh, just btw.. is it even possible to move data from an NFS to the trash?

It'll delete your entire collection just for **** and giggles


JUST KIDDING

Dan wrote:It'll delete your entire collection just for **** and giggles

))

You may not be able to move data from NFS to the trash, simply because of the nature of networked file systems, but I haven't confirmed.

Really?  That'll be annoying.  I've got an NFS share to supply music across my network, which amaroK won't be able to touch.  I still think my idea to add a "trash" note in the database is a good one.

why is amarok even allowed to delete files? can we please just remove that? i see no need. It's a music player not a file manager.

Dan wrote:It'll delete your entire collection just for **** and giggles

We have it setup now to interface with Web 2.0 services and automatically delete any **** music. Nifty feature, I hope you all enjoy.

As long as I can configure it to still work the old way...

feld wrote:why is amarok even allowed to delete files? can we please just remove that? i see no need. It's a music player not a file manager.

Would you please read the rest of the thread before making a comment like that?  We've got 3 pages of discussion about why amaroK can delete files, and the general concensus is that it's a useful feature which should definately be kept - with appropriate safeguards, of course.

if your argument is that amarok should have that ability to delete a file because it is a "Collemtion Manager" (i aggree with that argument), why not move that item into the context menu of the Collection Manager? That would be far more intuitive, since a Playlist entry semantically is not assiciated with a file at all - it could be a radio stream too. But a Collection entry is always a file if i don't miss something. What do you think about this idea to move "Delete File" from the Playlist context menu to the Collection context menu, and rename "Remove from playlist" into "Remove" ?

litb wrote:if your argument is that amarok should have that ability to delete a file because it is a "Collemtion Manager" (i aggree with that argument), why not move that item into the context menu of the Collection Manager? That would be far more intuitive, since a Playlist entry semantically is not assiciated with a file at all - it could be a radio stream too. But a Collection entry is always a file if i don't miss something. What do you think about this idea to move "Delete File" from the Playlist context menu to the Collection context menu, and rename "Remove from playlist" into "Remove" ?

Its already both places.

litb wrote:What do you think about this idea to move "Delete File" from the Playlist context menu to the Collection context menu, and rename "Remove from playlist" into "Remove" ?

You know, I absolutely agree with that.  I still think that my TrashDB idea is a good one, but in my opinion it would be far better to have the "Permanently Delete" option in the collection browser only.  I always worry about removing files from the playlist in case I delete them totally.

Also, I wasn't aware that the option existed to delete from the collection browser until you pointed it out, Ian - I didn't notice it hidden under the "Manage Files" submenu.  Maybe that's just me, though.