Add playlist reverse command

[floscr]

Describe your changes

Implements a reverse playlist command to reverse the order of tracks in a playlist.
Reverse was not implemented as a sort method, as I don't see it as a dynamic order, but as a do once command.
When reversing playlist we also clear the current sort order.

Adds it under the default keybinding Shift+R

Issue ticket number and link

N/A

Checklist before requesting a review

• Documentation was updated (i.e. due to changes in keybindings, commands, etc.)
• Changelog was updated with relevant user-facing changes (eg. not dependency updates, not performance improvements, etc.)

[Copilot]

Pull Request Overview

This PR implements a new playlist reverse command that reverses the order of tracks in a playlist and clears any stored sort preferences. The reverse functionality is treated as a one-time operation rather than a dynamic sort method, and it's bound to the Shift+R key combination.

• Adds a new Reverse command that reverses playlist track order
• Updates queue handling to properly maintain current track position after reversal
• Clears stored sort preferences when reversing to avoid conflicts

Reviewed Changes

Copilot reviewed 7 out of 7 changed files in this pull request and generated 2 comments.

Show a summary per file

File	Description
src/command.rs	Adds the Reverse command enum variant and parsing logic
src/commands.rs	Adds keybinding for Shift+R and includes Reverse in unsupported commands list
src/model/playlist.rs	Implements the reverse logic for playlist tracks and clears sort state
src/queue.rs	Implements queue reversal with proper current track index handling
src/ui/playlist.rs	Handles the reverse command in the playlist view
doc/users.md	Documents the new reverse command and keybinding
CHANGELOG.md	Records the new feature addition

[Copilot]

The calculation for the new index after reversing has a logical error. For a queue of length n, when reversing, the element at index i should move to index n - 1 - i. The current calculation queue.len().saturating_sub(1).saturating_sub(index) is equivalent to (n - 1) - index, which is correct. However, this will panic if index >= queue.len(), and saturating_sub won't help in that case. Consider adding a bounds check: if index < queue.len() { let new_index = queue.len() - 1 - index; *current = Some(new_index); }

Suggested change

	*current = Some(new_index);
	if index < queue.len() {
	let new_index = queue.len() - 1 - index;
	*current = Some(new_index);
	}

[hrkfdn]

Hi there, apologies for the late review. Generally I think this is a nice idea, but I wonder if this should be applicable to queues instead, which are more like a scrap playlist that can then be saved?

Because the way this is implemented right now will reverse playlists but there's no way to save them from the playlist view, right?

[floscr]

Hey no problem!

My use case was to quickly flip the order of items in a playlist where I add stuff and sort it over time.
This wouldn't have quite fit with the sort command, as sorting by added doesn't do the same once you re-arrange items in a playlist.
(In spotify this is called custom order and there's no quick way to reverse this list)

This command could possibly be extended to any view IMO,
but maybe a custom dynamic sort order would be a better fit (So reverse of no sort) and then having a quick way to toggle this.

But I do like the UX of having just a ":reverse" command.