-
-
Notifications
You must be signed in to change notification settings - Fork 763
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
ls --hyperlink shows error when clicked #6192
Comments
Hi munzirtaha, This isn't a Wezterm bug. The ls --hyperlink feature, always outputs a file:// protocol URL that includes the hostname. Think you'll have to report a bug with KDE. Edit: you might actually be able to make it work with a custom event handler, but the
|
Thanks a lot for the quick reply. In the beginning, I also thought
If |
Good point. Turns out Wezterm will keep trying each of these methods in turn until success:
So, it keeps going after the initial error that you see. This suggests another I |
But none of these commands would open the hyperlink in KDE
However, after the error, I don't know what other terminals do, but isn't it easy for |
As far as I can tell, Wezterm won't do anything else after those commands.
Yes, it'd be easy for it to remove file://localhost and file://$HOSTNAME |
I tested this as you said and it turned out the |
Close, but xdg-open is being called first. It detects that you're running KDE, so it calls kde-open, which generates an error. Wezterm calls gio next. The errors you see are not generated by Wezterm, it's just the error output generated by kde-open. But i'm not sure how you would see those, unless you are starting Wezterm at a command line. |
Ugh! So up until this point, I didn't understand that you were getting a popup window in your face,
I've never seen an interactive window displayed for any of these command-line utilities on any system ever. See something new every day :-) If it was my system, and everything else being equal, I'd just uninstall whatever package provides kde-open, Edit: uninstalling kde-open is a bad idea, since it would break xdg-open on your system too. Or you can use the wezterm lua "open-uri" handler from a few messages back to avoid the default
That would be great. But I think you have everything you need to make your system work well in the interim.
xdg-open doesn't exist on every system. And if xdg-open is successful, the others are never called anyway. |
Yes, with your help I already made my system work properly in different ways. I even, for playing sake, removed all those candidates and compiled wezterm with |
For reference, I found a bug already open at https://bugs.kde.org/show_bug.cgi?id=461756 two years ago. I have one suggestion that might be very trivial but solves the problem elegantly. Why not you just change the order and put the best candidate |
What Operating System(s) are you seeing this problem on?
Linux Wayland
Which Wayland compositor or X11 Window manager(s) are you using?
KDE
WezTerm version
wezterm 20240922-151228-2b76c63b
Did you try the latest nightly build to see if the issue is better (or worse!) than your current version?
Yes, and I updated the version box above to show the version of the nightly that I tried
Describe the bug
$ ls --hyperlink
Shows clickable file and folder names, but when I click on any folder I get:
Error - KIO Client The file or folder //lenovo/home/me/Pictures does not exist.
After clicking
OK
to the error, it will open the file or folder successfully.To Reproduce
$ ls --hyperlink
and click any file or folder name
Configuration
no config
Expected Behavior
No error
Logs
No response
Anything else?
No response
The text was updated successfully, but these errors were encountered: