Tested on Linux, desktop environment: KDE Plasma, file manager Dolphin.
If current file has comma in its name, locatefile opens not just its folder, but also another unrelated folder, probably the system default one, in my case it's /home/user/, aka ~/.
I guess this is a missing escaping issue. locatefile should try to escape comma in path. Currently, I believe it's causing , to be interpreted by command as an argument separator, thus launching two folders instead of just one.
Log:
mpv /tmp/tst,tst.mp4 --msg-level='locatefile=debug'
[locatefile] Loading lua script /home/user/.config/mpv/scripts/locatefile.lua...
[locatefile] loading mp.defaults
[locatefile] loading file /home/user/.config/mpv/scripts/locatefile.lua
(+) Video --vid=1 (*) (h264 720x1280 29.952fps)
(+) Audio --aid=1 (*) (aac 1ch 44100Hz)
AO: [pulse] 44100Hz mono 1ch float
VO: [gpu] 720x1280 yuv420p
(Paused) AV: 00:00:00 / 00:00:29 (2%) A-V: 0.000
[locatefile] File detected '/tmp/tst,tst.mp4', your OS file browser will be launched.
[locatefile] Linux detected.
[locatefile] Command to be executed: 'dbus-send --print-reply --dest=org.freedesktop.FileManager1 /org/freedesktop/FileManager1 org.freedesktop.FileManager1.ShowItems array:string:"file:/tmp/tst,tst.mp4" string:""'
method return time=1664780033.610051 sender=:1.575 -> destination=:1.954 serial=2768 reply_serial=2
Tested on Linux, desktop environment: KDE Plasma, file manager Dolphin.
If current file has comma in its name, locatefile opens not just its folder, but also another unrelated folder, probably the system default one, in my case it's
/home/user/, aka~/.I guess this is a missing escaping issue. locatefile should try to escape comma in path. Currently, I believe it's causing
,to be interpreted by command as an argument separator, thus launching two folders instead of just one.Log: