[Question] History not logged when opening files in joshuto with `fork = true` option

[po5]

[Question] History not logged when opening files in joshuto with `fork = true` option

[po5]

The history file is being written to correctly, but this program doesn't feed the absolute path of your file to mpv, only its filename, and the working directory is wrong.
You will encounter this when the directory containing your file is not the one you launched joshuto in.

Properties after launching joshuto from /home/eva/Downloads and navigating to open /home/eva/Documents/1234/potato.flac with mpv:

[memo] stream-open-filename potato.flac
[memo] path potato.flac
[memo] working-directory /home/eva/Downloads

As a result /home/eva/Downloads/potato.flac is what gets written to the history file. It doesn't show up with default memo settings as files that don't exist are hidden.

This is a bug in your program so please file an issue there, works fine in ranger and other file managers:

[memo] stream-open-filename /home/eva/Documents/1234/potato.flac 
[memo] path /home/eva/Documents/1234/potato.flac 
[memo] working-directory /home/eva/Documents/1234

If you or the maintainer truly believes joshuto does nothing wrong, file a report with mpv as that would mean their working directory resolution is wrong.

[po5]

Could this be the offending commit? Try reverting it. kamiyaa/joshuto@ea79ae0

[xfzv]

This is a bug in your program so please file an issue there, works fine in ranger and other file managers

Indeed, it works fine with gokcehan/lf and jarun/nnn on my end too. I should have tried other terminal file managers first...

Could this be the offending commit? Try reverting it. kamiyaa/joshuto@ea79ae0

Unfortunately I'm not technical enough to deal with the merge conflicts I'm running into after reverting this commit. I tried to use git reset --hard but got a lot of cargo errors when trying to build joshuto.

Thank you for your help, as always. 👌