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

Create interactive import process #2

Open
nsp opened this issue Sep 9, 2012 · 4 comments
Open

Create interactive import process #2

nsp opened this issue Sep 9, 2012 · 4 comments

Comments

@nsp
Copy link
Contributor

nsp commented Sep 9, 2012

For people that don't quite understand what every dotfile in their $HOME does, but want to see each file as it's added. Useful for people that don't want to accidentally add e.g. private keys/passwords.

@justone
Copy link
Owner

justone commented Oct 19, 2012

Can you describe the use case for this feature? What's the sequence of commands?

@nsp
Copy link
Contributor Author

nsp commented Oct 19, 2012

For brand new users of dfm, importing dotfiles for the very first time on their very first machine. I'd love to be able to do 'dfm import .*' but of course that matches every file in the current directory and parent directory, as well as private keys and other things I wouldn't want managed.

I imagine this behaving like 'git add -i' if you're looking for UX inspiration. For each file, the user is presented the file name and path, and can add/view/recurse/skip each file/directory.

I'm still not sure yet how git subtrees work, would it be possible to detect that a folder is a repo and then squash add it as a subtree?

@justone
Copy link
Owner

justone commented Oct 20, 2012

Cool. That makes sense. I updated the title of the issue to say 'import' instead of 'install'.

As far as subtrees go, I'm pretty sure it would be impossible to detect that a folder is a subtree because you would need to know what other git repo it's a subtree merge of.

@nsp
Copy link
Contributor Author

nsp commented Oct 21, 2012

On the initial import, there are no subtrees, right? Just full repositories you can 'git rev-parse', right?

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

No branches or pull requests

2 participants