FS#51 - $XDG_DATA_HOME assumed to be set
Attached to Project:
Uzbl
Opened by Anonymous Submitter - 2009-06-25 08:34:16 PM
Last edited by Anonymous Submitter - 2010-04-22 08:41:58 PM
Opened by Anonymous Submitter - 2009-06-25 08:34:16 PM
Last edited by Anonymous Submitter - 2010-04-22 08:41:58 PM
|
DetailsThe example scripts make use of $XDG_DATA_HOME, but they assume it is set. The XDG spec says that if it is not set, scripts should default to "$HOME/.local/share"
|
This task depends upon
Closed by Anonymous Submitter
2010-04-22 08:41:58 PM
Reason for closing: Fixed
Additional comments about closing: The XDG paths are exported in uzbl-browser and there is logic inside uzbl-core to use the default XDG data dirs if they are not set in your environ.
2010-04-22 08:41:58 PM
Reason for closing: Fixed
Additional comments about closing: The XDG paths are exported in uzbl-browser and there is logic inside uzbl-core to use the default XDG data dirs if they are not set in your environ.
$ echo $XDG_DATA_HOME
$ uzbl
Icon "./uzbl.png" not found. ignoring.
error on run_command: Failed to execute child process "$XDG_DATA_HOME/uzbl/scripts/history.sh" (No such file or directory)
error on run_command: Failed to execute child process "$XDG_DATA_HOME/uzbl/scripts/cookies.py" (No such file or directory)
...
error on run_command: Failed to execute child process "$XDG_DATA_HOME/uzbl/scripts/cookies.py" (No such file or directory)
error on run_command: Failed to execute child process "$XDG_DATA_HOME/uzbl/scripts/history.sh" (No such file or directory)
set history_handler = sh ${XDG_DATA_HOME:-$HOME/.local/share}/uzbl/scripts/history.sh
but in the case of python....
uzbl-core however, still doesn't have this functionality built in. so i guess we still need to fix that, but it's less critical as most people will use uzbl-browser