-
Notifications
You must be signed in to change notification settings - Fork 3
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
Use xdg-open to open the native file manager on Linux #284
Comments
Interesting, I did not know this. I just implemented your suggestion. It will be released with the next version of fman (usually in a couple of days). You will be notified of the new version automatically. |
Implemented in fman 0.8.3. :) |
Thanks for the fix :) Unfortunately it doesn't seem to work for me (just updated fman via apt) - same Popen error message as before. Do I need to reset the settings or something first? |
When you initially encountered the problem, did you fix it by editing the settings? |
No (where are the settings btw? Typing "setting" in the command pallet yields no results). |
Here is the revant page of fman's documentation: https://fman.io/docs/terminal. The file you want to look at is |
Re-opening this issue until it's confirmed fixed. |
The file doesn't exist:
|
Then you have the default settings and for some reason the way fman launches |
(Sorry it's not working btw) |
Yes, exactly like before with 0.8.2.
No problem ;) Must be quite some work for you to support Linux in the first place. |
Ah, I think I know why. Let me fix this for the next version of fman. |
fman 0.8.6 is out. Can you let me know whether it fixes the issue for you @jhasse ? |
Yes, works perfectly! Thank you very much :) |
Cool! Thx for letting me know :-) |
I've just tried fman on Ubuntu MATE 17.10 and pressing F10 won't open my native file manager but tell me to configure it. It would be great if this wasn't required and fman would use
xdg-open {curr_dir}
instead, as that should work for most (if not all) desktop environments.The text was updated successfully, but these errors were encountered: