-
-
Notifications
You must be signed in to change notification settings - Fork 92
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
mime type check leaks error message into prompt #133
Comments
Further notes, the file is opened when telling Telescope to open it, so it appears this is just a visual issue and not prohibitive to work flow. |
fd, for what its worth i've also seen this with live grep and other pickers but couldnt track it down yet. It only appeared randomly for me. I'll have to try these reproduce steps later |
It's the Commenting out mime-type checking immediately or using I hope to be able to complete the previewer RFC before 0.1 but have an important conference deadline end of June. Let's see. I have no sense of urgency to quick fix this stand alone as I suppose it's a rather rare issue 😅 |
Description
If you have a file with a truly awful file name (for example
hello world %^&*()_-="'<,>.?|[{]}\
), Telescope barfs and drops an error in the input box telling you thatsh
has cant resolve the name correctly. This error does not go away unless you close and reopen the file browser (and dont navigate to the awful file).Discovered while testing another plugin and verified on my machine.
Neovim version
Operating system and version
Ubuntu 20.04
Steps to reproduce
$ touch "garbage%^&*()_-=\"'<,>.?|[{]}\"
Expected behavior
Telescope File Browser should be able to handle awful (but technically valid) file names
Actual behavior
String quoting failure it looks like?
Minimal config
The text was updated successfully, but these errors were encountered: