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
{{ message }}
Repository navigation
files created in ~/bin, even if another file of the same name already exists #22
That's true. Mostly it does it for "easy" upgrades, but the case where it's replacing a completely different file instead of an older version of the same script is pretty nasty.
These cases could be differentiated by looking for .conscript/sbt-launch.jar in the file. If that's not found, refuse to replace and let the user sort it out.
Activity
n8han commentedon Sep 11, 2011
That's true. Mostly it does it for "easy" upgrades, but the case where it's replacing a completely different file instead of an older version of the same script is pretty nasty.
kevinwright commentedon Sep 11, 2011
Guess what my case was :)
n8han commentedon Sep 11, 2011
These cases could be differentiated by looking for
.conscript/sbt-launch.jarin the file. If that's not found, refuse to replace and let the user sort it out.kevinwright commentedon Sep 11, 2011
I'd be happy for the existing file to be renamed, append .bak1, .bak2 etc to the name. Or some other scheme.
eed3si9n commentedon May 15, 2016
Conscripted scripts are now created under
$CONSCRIPT_BIN(default~/.conscript/bin/). Do we still need backup feature?