Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

files created in ~/bin, even if another file of the same name already exists #22

Open
kevinwright opened this issue Sep 10, 2011 · 5 comments
Open

files created in ~/bin, even if another file of the same name already exists #22

kevinwright opened this issue Sep 10, 2011 · 5 comments
Labels
NeedsInfo

Comments

@kevinwright
Copy link

A prompt would be nice, or at least rename any existing files as a backup!
@n8han
Copy link

n8han commented 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
Copy link
Author

Guess what my case was :)

@n8han
Copy link

n8han commented Sep 11, 2011

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.

@kevinwright
Copy link
Author

I'd be happy for the existing file to be renamed, append .bak1, .bak2 etc to the name. Or some other scheme.

@hanxue hanxue mentioned this issue Nov 28, 2013
Open
@eed3si9n
Copy link
Member

Conscripted scripts are now created under $CONSCRIPT_BIN (default ~/.conscript/bin/). Do we still need backup feature?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
NeedsInfo
Milestone
No milestone
Development

No branches or pull requests
3 participants
@kevinwright @n8han @eed3si9n