In the documentation it's mention that if the file pt-stalk.conf exists in the current working directory, then “ENVIRONMENT” variables are imported from it. But in fact if pt-stalk is in the path, it won't use the config file in the current working dir but in the directory from the command.
This is a patch:
--- pt-stalk.old 2011-10-23 10:01:24.633878128 +0200
+++ pt-stalk 2011-10-23 10:02:54.877878121 +0200
@@ -7,8 +7,8 @@
# ########################################################################
# Check for the existence of a config file and source it if it exists
# ########################################################################
-if [ -f "${0}.conf" ]; then
- . "${0}.conf"
+if [ -f "$(basename ${0}).conf" ]; then
+ . "$(basename {0}).conf"
fi
In the documentation it's mention that if the file pt-stalk.conf exists in the current working directory, then “ENVIRONMENT” variables are imported from it. But in fact if pt-stalk is in the path, it won't use the config file in the current working dir but in the directory from the command.
This is a patch:
--- pt-stalk.old 2011-10-23 10:01:24.633878128 +0200 ####### ####### ####### ####### ####### ####### ####### ####### ####### ## ####### ####### ####### ####### ####### ####### ####### ####### ####### ##
+++ pt-stalk 2011-10-23 10:02:54.877878121 +0200
@@ -7,8 +7,8 @@
# #######
# Check for the existence of a config file and source it if it exists
# #######
-if [ -f "${0}.conf" ]; then
- . "${0}.conf"
+if [ -f "$(basename ${0}).conf" ]; then
+ . "$(basename {0}).conf"
fi
# ####### ####### ####### ####### ####### ####### ####### ####### ####### ####### #