[GH-ISSUE #727] [Feature Request] Search history and reverse search #291

New issue

Open

opened 2026-02-28 14:48:17 +03:00 by kerem · 2 comments

kerem commented

2026-02-28 14:48:17 +03:00

Owner

Originally created by @jayache80 on GitHub (Jan 27, 2021).
Original GitHub issue: https://github.com/Rigellute/spotify-tui/issues/727

I find myself listening to things over and over and over, and don't like to type the full artist/album/song/whatever each time.

It would be great if all the Search Input entries that are made were stored in a history file, perhaps:

~/.config/spotify-tui/.search_history

similar to how bash will store previous command line entries in the $HISTFILE file.

Then, listen for Ctrl+R in the Search Input box and reverse search your previous Search Input entries. This way you could type a few characters and quickly repeat a previous search. Similarly Ctrl+P (or ↑) and Ctrl+N (or ↓) would traverse up and down the history as you'd expect.

Originally created by @jayache80 on GitHub (Jan 27, 2021). Original GitHub issue: https://github.com/Rigellute/spotify-tui/issues/727 I find myself listening to things over and over and over, and don't like to type the full artist/album/song/whatever each time. It would be great if all the Search Input entries that are made were stored in a history file, perhaps: ``` ~/.config/spotify-tui/.search_history ``` similar to how `bash` will store previous command line entries in the `$HISTFILE` file. Then, listen for <kbd>Ctrl</kbd>+<kbd>R</kbd> in the Search Input box and reverse search your previous Search Input entries. This way you could type a few characters and quickly repeat a previous search. Similarly <kbd>Ctrl</kbd>+<kbd>P</kbd> (or <kbd>↑</kbd>) and <kbd>Ctrl</kbd>+<kbd>N</kbd> (or <kbd>↓</kbd>) would traverse up and down the history as you'd expect.

kerem commented

2026-02-28 14:48:17 +03:00

Author

Owner

@jayache80 commented on GitHub (Feb 19, 2021):

I started working on this but it was getting more and more hacky. What are the thoughts on bringing in a bona fide readline library, like rustyline?

@jayache80 commented on GitHub (Feb 19, 2021): I started working on this but it was getting more and more hacky. What are the thoughts on bringing in a bona fide readline library, like [rustyline](https://github.com/kkawakam/rustyline)?

kerem commented

2026-02-28 14:48:17 +03:00

Author

Owner

@jayache80 commented on GitHub (Feb 20, 2021):

On second thought, after trying a few examples, I see the difficulties in combining tui-rs and rustyline. Until some sort of readline paradigm is established upstream in the tui-rs user input widget, it seems the best way is to implement more "pseudo-readline" features in handlers/input.rs as the codebase is already doing.

I have something working and I'll submit a pull-request soon.

@jayache80 commented on GitHub (Feb 20, 2021): On second thought, after trying a few examples, I see the difficulties in combining tui-rs and rustyline. Until some sort of readline paradigm is established upstream in the tui-rs user input widget, it seems the best way is to implement more "pseudo-readline" features in handlers/input.rs as the codebase is already doing. I have something working and I'll submit a pull-request soon.