-
Notifications
You must be signed in to change notification settings - Fork 25
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
Opening url encoded file paths #31
Comments
@bloody-scythe thanks for reporting this, will look into it |
Hi @chmln I got a similar error look like the one in this link. (https://bbs.archlinux.org/viewtopic.php?id=207758) Thank you so much for your attention, time and efforts. |
@bloody-scythe @hukacode should be fixed in the latest release :) |
Hi @chmln I still get this issue with version 0.6.1 Best regards, |
@hukacode It was definitely a handlr issue. I just published a fix so it should work in v0.6.3 now |
Hi @chmln This is an error when I open with v0.6.3 In previous version, I can open "location" with file manager, but now I get this error |
Ahhhh I see what's happening. The path gets urlencoded. When I was testing the fix locally I didn't think to check a file with spaces. Now I just have olto urldecode the path before passing it to the program. Thanks @hukacode ! |
So...
Handlr seems to pass uri file paths directly to the program (differently from xdg-open) which some programs are not ready to handle.
That make the file not to be found.
example:
file://home/user/file.png
isn't parsed to
/home/user/file.png
The text was updated successfully, but these errors were encountered: