You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Thank you for Baton, loving it so far. I have only one annoyance so far, and I wanted to get your feedback.
My listening is oriented around albums. Which is why I appreciate being able to do a "baton search artist NAME", select an artist, and then using the right arrow, go ahead and select a specific album, or even a song. However, after hitting play and exiting the view, I don't have a way to return to it. I can hit the up arrow and repeat the original search, but that requires me to start again from the artist and the album. The same problem exists when playing a song from a playlist using "baton me playlists".
Would it make sense to implement a command that shows the last screen again? Something like "baton current" or "baton list"? I'd be happy to send a pull request if you provide details on how you'd like it to work. I am guessing that the main problem is figuring out how to cleanly save state as the user moves through the tables.
The text was updated successfully, but these errors were encountered:
Thank you for Baton, loving it so far. I have only one annoyance so far, and I wanted to get your feedback.
My listening is oriented around albums. Which is why I appreciate being able to do a "baton search artist NAME", select an artist, and then using the right arrow, go ahead and select a specific album, or even a song. However, after hitting play and exiting the view, I don't have a way to return to it. I can hit the up arrow and repeat the original search, but that requires me to start again from the artist and the album. The same problem exists when playing a song from a playlist using "baton me playlists".
Would it make sense to implement a command that shows the last screen again? Something like "baton current" or "baton list"? I'd be happy to send a pull request if you provide details on how you'd like it to work. I am guessing that the main problem is figuring out how to cleanly save state as the user moves through the tables.
The text was updated successfully, but these errors were encountered: