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
I'm having an issue where modd fails on my remote dev system. The reason, I believe, is because my home dir appears to be a symlink (readlink -f returns real path). Paths returned by @mods and $(pwd)/theFileInQuestion are very different.
This makes all patterns fail, except those that use **, which accounts for differences by virtue of how it works.
However, when using ** in this situation, then indir will fail with a fork/exec: no such file. The obvious fix is to put the equivalent command into the prep directive (cd something && ...).
So far, this looks like the best workaround, to prepend all patterns with ** and include directory changes into the prep directive.
The text was updated successfully, but these errors were encountered:
I'm having an issue where modd fails on my remote dev system. The reason, I believe, is because my home dir appears to be a symlink (
readlink -f
returns real path). Paths returned by@mods
and$(pwd)/theFileInQuestion
are very different.This makes all patterns fail, except those that use
**
, which accounts for differences by virtue of how it works.However, when using
**
in this situation, thenindir
will fail with afork/exec: no such file
. The obvious fix is to put the equivalent command into theprep
directive (cd something && ...
).So far, this looks like the best workaround, to prepend all patterns with
**
and include directory changes into the prep directive.The text was updated successfully, but these errors were encountered: