-
Notifications
You must be signed in to change notification settings - Fork 282
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
Files with spaces in their name are not parsed correctly #145
Comments
Can you try using 0.6.0 by any chance? We added filesystem validation: So we can actually parse files with spaces in them now :) You should be able to upgrade via brew since thats the latest version: Or just clone the repo and do |
The hyphens stuff will be easy to add, thats just a regex change. closing this out since im pretty sure we have files with spaces working, but reopen if you can repro on 0.6 |
Are you talking about the |
None of the files above were selectable except the bottom one. Does the hyphen issue effect hyphens in folders as well as extensions? If not I'd expect Update: Confirmed that this issue persists on master. Sorry for the pain. Sublime configuration files are admittedly an awful hodge-podge of edge cases for this type of thing. |
Ah dang ok I'll take another look at this then |
Ah this was easy to fix -- just needed to allow extensions to have hyphens in the regex that allows spaces :O woof. #149 should go in clean and then we are good! |
Resolves #145 Allow combining hyphes and spaces and everything
Confirmed that this all looks good now on master. Thanks! I'm excited about this project and have been enjoying using it. |
Great to hear @benmccormick ! 😍 feel free to drop by and open issues in the future for other bugs / improvements |
When seeing file paths that have a space in them (yes clearly not ideal), fpp cuts off early or starts partway through
This is with fpp version 0.5.7.
This image also shows the hyphenated extensions issue from #144
The text was updated successfully, but these errors were encountered: