I discovered that fluxbox causes this problem: starting from command line ("foobar") or from thunar "Open WIth foobar" on a file, it works fine; when I start it with a fluxbox key-mapping, it scans the home directory.
Starting from thunar/"Open With" mp3 file:
$ ps -ef | grep foobar
... 2293 1 0 14:26 ? 00:00:00 /bin/sh /home/me/bin/foobar /home/me/Downloads/Bo_Diddley--LV--Old_Smokey.mp3
... 2300 2293 6 14:26 ? 00:00:00 c:\Pgms\foobar2000\foobar2000.exe Z:\home\me\Downloads\Bo_Diddley--LV--Old_Smokey.mp3
Starting from fluxbox (line in file "keys": "87 :Exec foobar":
$ ps -ef | grep foobar
... 2323 1290 0 14:27 ? 00:00:00 /bin/bash -c foobar
... 2328 2323 15 14:27 ? 00:00:00 c:\Pgms\foobar2000\foobar2000.exe Z:\home\me\
So the fluxbox's "Exec foobar" is sticking "Z:\home\me\" on the end of the command, and foobar scans it.
SOLVED:
"foobar" command line or thunar/"Open with":
- Code: Select all
#!/bin/sh
QUICKPARLOCATION="c:\\Pgms\\foobar2000\\foobar2000.exe"
PARAM=`winepath -w "$*"`
wine "$QUICKPARLOCATION" "$PARAM"
exit 0
foobarflux for "Exec foobarflux" from "Keys" file:
- Code: Select all
#!/bin/sh
cd /home/me/.wine/drive_c/Pgms/foobar2000/
wine foobar2000.exe /add "$*"
exit 0
The latter version doesn't pass any arguments to foobar.