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.

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

Better support for cloning to a different directory name? #185

Open
rchady opened this issue Oct 22, 2015 · 1 comment
Open

Better support for cloning to a different directory name? #185

rchady opened this issue Oct 22, 2015 · 1 comment
Labels

Comments

@rchady
Copy link

rchady commented Oct 22, 2015

Is there a better way to clone a repository to a different name than it is hosted under? For example, normally with git you can do

git clone git@host.com:repo some_other_name

and it will work. If you do that with vcsh, it just changes the name of the directory used in .config/vcsh/repo.d and just drops the files in to $HOME.

I know about VCSH_BASE, but the usage pattern seems backwards to me. I would rather have an env variable to set for changing the repo.d directory name and allow specifying where to check something out to on the command line.

This would allow you to do things like

vcsh clone git@host.com:repo .some_other_dir

and it would place the files in to $PWD/.some_other_dir, just like git normally would. This would make vcsh much easier to use for things outside of just managing $HOME files.

@RichiH
Copy link
Owner

RichiH commented Nov 29, 2015

This sounds similar to what the agnostic branch tries to do.

The short answer is that there are a lot of ways to shoot your own foot with that and I would need a way to be sure that's not too likely to happen.

#115
https://github.com/RichiH/vcsh/tree/feature/agnostic

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants