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

Feature idea: When I add a file in .vim/, it doesn't get added to ~/.../src/mascip-dots/.vim/ #11

Open
mascip opened this issue Feb 28, 2014 · 0 comments

Comments

@mascip
Copy link

mascip commented Feb 28, 2014

This feature could easily be added by creating symlinks on folders, rather than symlinks on files:

ln -s .vim ~/.../src/mascip-dots/.vim ~/.vim 

Any file created in .vim/ would simultaneously be created in ~/.../src/mascip-dots/.vim

It would break compatibility with loop-dots, so it might not be desirable. Maybe we could have a 4th install method, which wouldn't be compatible with loop-dots:

  • copy
  • hardlink
  • symlink
  • symlink-folders # Not compatible with loop-dots

One (small) problem that we might encounter with this solution, would be if some function needs to know which install method has been used (we could save this info in a file). Probably some of the functions who use

_all_files()

I don't think that do_backup(), do_restore(), do_list(), do_remove() would need this information, but it's worth checking and keeping it in mind.

Is that a plain bad idea, or is there something positive in that? For my own use, I hate realizing that I've added files in subfolders of ~, rather than in subfolders of ~/.../src. But maybe there's a simpler way to handle this problem.

Maybe a new command line function that copies files added to my subfolders, into the right corresponding subfolders of .../src/ ? It still wouldn't work with loop-dots, but it's just about creating this one new function, rather than having to modify all the others.

What do you think?
Did this ever happen to you? Do you have a simpler solution that you use in this scenario?

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

No branches or pull requests

1 participant