[GH-ISSUE #181] Pagination of playlists #93

Closed
opened 2026-02-28 14:46:58 +03:00 by kerem · 4 comments
Owner

Originally created by @screamuch on GitHub (Dec 2, 2019).
Original GitHub issue: https://github.com/Rigellute/spotify-tui/issues/181

I cannot scroll past the "first page" of any playlist, meaning instead of scrolling through every song in the playlist, the UI loops through whatever is on the screen.

Example:
When I go to my Library/Playlist section and scroll down, everything is fine, I can scroll through all the entries. When I try to do so in the Songs section and reach the bottom entry, it just loops me back to the first song in a given playlist.

P.S.
I've looked into #150 but it doesn't seem to support actual playlists, rather lists of playlists.

Originally created by @screamuch on GitHub (Dec 2, 2019). Original GitHub issue: https://github.com/Rigellute/spotify-tui/issues/181 I cannot scroll past the "first page" of any playlist, meaning instead of scrolling through every song in the playlist, the UI loops through whatever is on the screen. Example: When I go to my Library/Playlist section and scroll down, everything is fine, I can scroll through all the entries. When I try to do so in the Songs section and reach the bottom entry, it just loops me back to the first song in a given playlist. P.S. I've looked into #150 but it doesn't seem to support actual playlists, rather lists of playlists.
kerem closed this issue 2026-02-28 14:46:59 +03:00
Author
Owner

@Rigellute commented on GitHub (Dec 2, 2019):

This is confusing for sure - essentially there are two types of scrolling at the moment

  1. Purely UI based
  2. Spotify result page based

The first type currently wraps when you get to the last result. This is not intuitive for sure. When the user gets to the last result in the list, pressing down should send a request for the next result page.

I have made a bit of a mess when it comes to handling pagination, so not every screen currently supports it.

See here for more info https://github.com/Rigellute/spotify-tui/issues/113

<!-- gh-comment-id:560309332 --> @Rigellute commented on GitHub (Dec 2, 2019): This is confusing for sure - essentially there are two types of scrolling at the moment 1. Purely UI based 1. Spotify result `page` based The first type currently wraps when you get to the last result. This is not intuitive for sure. When the user gets to the last result in the list, pressing down should send a request for the next result page. I have made a bit of a mess when it comes to handling pagination, so not every screen currently supports it. See here for more info https://github.com/Rigellute/spotify-tui/issues/113
Author
Owner

@screamuch commented on GitHub (Dec 3, 2019):

Oh, thanks for referring me to the right place, @Rigellute!

I've found out that playlist pagination has is done through control-d and control-u. Works like a charm with my playlists.

Couldn't find this info in any of the docs. I've tried README.md, ? in-app. Are there any other places that describe user controls? I could make a PR that adds this info to the docs.

<!-- gh-comment-id:560938187 --> @screamuch commented on GitHub (Dec 3, 2019): Oh, thanks for referring me to the right place, @Rigellute! I've found out that playlist pagination has is done through `control-d` and `control-u`. Works like a charm with my playlists. Couldn't find this info in any of the docs. I've tried `README.md`, `?` in-app. Are there any other places that describe user controls? I could make a PR that adds this info to the docs.
Author
Owner

@Rigellute commented on GitHub (Dec 3, 2019):

This is in the help menu, but I agree it is not that clear or obvious.
image

<!-- gh-comment-id:561129237 --> @Rigellute commented on GitHub (Dec 3, 2019): This is in the help menu, but I agree it is not that clear or obvious. <img width="1153" alt="image" src="https://user-images.githubusercontent.com/12150276/70048005-2ca36a80-15c1-11ea-8878-c0dcc03470ae.png">
Author
Owner

@Rigellute commented on GitHub (Dec 3, 2019):

Anyway, thanks for confirming that this works! Will think about how to make this more obvious.

<!-- gh-comment-id:561129451 --> @Rigellute commented on GitHub (Dec 3, 2019): Anyway, thanks for confirming that this works! Will think about how to make this more obvious.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/spotify-tui#93
No description provided.