We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The search bar on the beet web interface functions as if the entire query was passed as a single argument to "beet list"
If you have a song titled "Word1 Word2 Word3", you can search for it like so:
beet ls Word1 Word3
Performing the same search on the web interface will not find any songs.
Word1 Word3
From my observations, the web plugin treats the entire query as a single argument, leading to the same (nonexistant) results that would be found of:
beet ls "Word1 Word3
The text was updated successfully, but these errors were encountered:
4f3cd65
Thanks! Just committed a client-side fix that splits on whitespace.
Sorry, something went wrong.
Fix confirmed in 69b7d1f
No branches or pull requests
The search bar on the beet web interface functions as if the entire query was passed as a single argument to "beet list"
If you have a song titled "Word1 Word2 Word3", you can search for it like so:
Performing the same search on the web interface will not find any songs.
From my observations, the web plugin treats the entire query as a single argument, leading to the same (nonexistant) results that would be found of:
The text was updated successfully, but these errors were encountered: