You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For external scripts, ensure that the working directory is set to the script path
For example, if a script is in /tmp/scriptname.sh, LUCID should run it with a working directory of /tmp.
This would avoid users having to manually do a cd /absolute/path or a cd $(BASH_SOURCE...)-style incantation
Background
I haven't dug into the code just yet, so perhaps something else is wrong here. Anecdotally, I've had a couple people fix their LUCID commands by just cd'ing to the appropriate path as a first step in their script
The text was updated successfully, but these errors were encountered:
Suggestion
/tmp/scriptname.sh
, LUCID should run it with a working directory of/tmp
.cd /absolute/path
or acd $(BASH_SOURCE...)
-style incantationBackground
I haven't dug into the code just yet, so perhaps something else is wrong here. Anecdotally, I've had a couple people fix their LUCID commands by just
cd
'ing to the appropriate path as a first step in their scriptThe text was updated successfully, but these errors were encountered: