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
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?
The text was updated successfully, but these errors were encountered:
This feature could easily be added by creating symlinks on folders, rather than symlinks on files:
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:
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
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?
The text was updated successfully, but these errors were encountered: