I have this simple script to use with seventh sense (it's a lone wolf gamebook reader/player):
#!/bin/bash GAME_PATH=$(dirname "$(readlink -f "$0")") SEVENTH_SENSE_PATH=$(echo ~)"/.wine/drive_c/users/"$(whoami)"/Documents" mkdir -p $SEVENTH_SENSE_PATH ln -s -f "$GAME_PATH/Lone Wolf/books" "$SEVENTH_SENSE_PATH/Seventh Sense" cd "$GAME_PATH/Lone Wolf" wine Lone\ Wolf.exe
It's very simple, only moving a directory inside the folder to the location that this windows program expects it on the wine dir - but that is not the problem.
ln here works the first time (it creates a symlink to
Seventh Sense inside the
Documents folder of the wine user. The problem is, the second time it makes a
books symlink inside the folder that the
Seventh Sense symlink points to (ironically, exactly the original
books folder), when run twice.
It causes no harm, but it seems like an obvious bug that is escaping me.
books is a folder (inside the
Lone Wolf folder that is at the same level as the script)).