New issue

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

--enqueue-files fails for commas in filenames #1773

Closed
Jimi-James opened this Issue Dec 28, 2015 · 3 comments

Comments

Projects
None yet
2 participants
@Jimi-James

Jimi-James commented Dec 28, 2015

Simple problem. I'm trying to enqueue filenames that have commas in an automated script, but since , is the delimiter, I have to somehow work around the filenames that have them. So, I tried escaping each comma with a , but that doesn't seem to work. Then, I tried wrapping each filename in quotes. That has opened up a big nest of issues I don't understand that I'm trying to work through over at http://stackoverflow.com/questions/34498976/quodlibet-suddenly-wont-accept-file-list-unless-i-manually-type-it-in , but the basic summary is, quodlibet doesn't play nice when I have double quotes in a sed line. My question is, what am I supposed to do if I want to automatically (not by manually typing the filenames in) enqueue songs that have commas in their filenames? Is there an escape character I don't know about, and if so, why isn't it the obvious backslash?

@declension declension added the bug label Dec 28, 2015

@declension declension changed the title from --enqueue-files: what to do when filenames have commas? to --enqueue-files fails for commas in filenames Dec 28, 2015

@declension

This comment has been minimized.

Member

declension commented Dec 28, 2015

Thanks for the report

@declension declension self-assigned this Dec 28, 2015

@declension

This comment has been minimized.

Member

declension commented Dec 29, 2015

Backslashed commas should now work, but for your use case you will probably get a cleaner solution using enqueue with the control file, thus avoiding any comma-escaping and newline-conversion in the first place...

@Jimi-James

This comment has been minimized.

Jimi-James commented Dec 29, 2015

Whoa. I've never heard of the control file before. That's pretty great. Solved it for me!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment