Continue even if script returns errors
Review Request #125323 - Created Sept. 20, 2015 and submitted
/bin/sh stops execution upon finding a nonzero exit code, which means that startkde will not continue if a script in .config/plasma-workspace/env/ produces an error. This small fix will execute a no-op in such a case, so that errors will not affect startkde's progress, while still being visible in .xsession-errors.
Tested both env-old.sh and env-new.sh with envvars.sh in ./testing, which refers to a location that no longer exists on my system. Confirmed that only env-new.sh performs the echo at the end.
The scripts are being sourced in a subshell, so echo will work, but the sourced variabled are then discarded.
It should be
test -r "$file" && . "$file" || true(lets use
:for better clarity?)