Installation of plugins via ./install about dotfiles HOT 10 CLOSED

This is independent of Dotbot. E.g. Vim 8 will automatically load packages in a particular directory (https://shapeshed.com/vim-packages/). You can put them there using Git submodules.

from dotfiles.

Thank you for this crash course in maintaining plugins without git repos! Unfortunately I think I had the impression that plugins must have a corresponding plugin manager. Most popular ones automatically use git clone instead of git submodule add, and I think I was looking in the wrong place in trying to modify the plugin managers to use submodules instead of repos. Now I know better!

from dotfiles.

I wouldn't modify the .gitmodules file directly. You can use the git submodule family of commands, e.g. git submodule add, to add them.

from dotfiles.

Has this been documented somewhere? I believe the way that things work in Vim plugin managers is that you execute some ex command like :PlugInstall and the plugin manager clones the repos for you in the appropriate folder. Does this mean you would have to add submodules for those repositorys manually to be compatible with dotbot (and not have git repos inside a submodule?)

from dotfiles.

I see.. Please excuse my inexperience. In summary, the way these dotfiles work for plugins is that using Git submodules, the Github repo for the plugin is "cloned" using git submodule add ... to the appropriate directory.

If we want to remove the plugin, we simply modify .gitmodules as done here: b1f82c9? Do we remove the files as shown here or did you do something different for that commit?

Do we still need to do this step using this method: Run rm -rf .git/modules/path_to_submodule (no trailing slash) when removing a submodule or will git handle it?

from dotfiles.

Yes, that's correct, I use git submodule add to clone the plugin as a submodule. When the dotfiles directory is cloned, the git submodule update ... command is used to check out the appropriate versions of all the submodules. Reading the documentation on submodules might help with understanding this.

To remove a plugin, you can just git rm the file, and Git will know that it's a submodule and make the appropriate modifications to .gitmodules. If you look at b1f82c9, you'll see that the .gitmodules file was edited (automatically by git, when I ran git rm), and the emacs.d/vendor/undo-tree submodule reference was also deleted.

from dotfiles.

Regarding submodules, is there any relevance to ignore=untracked as in your .gitmodules:

[submodule "vim/bundle/vim-markdown"]
	path = vim/pack/vendor/start/vim-markdown
	url = https://github.com/tpope/vim-markdown
	ignore = untracked

It's relevant when e.g. untracked temporary files are created in submodule directories.

from dotfiles.

Does this shell command from .install.conf.yaml achieve something similar? Deleting the untracked files (even in those submodules that have ignore = untracked) to create a fresh dotfiles directory every time ./install is run? (BTW perhaps you should call this on vim/pack/vendor instead of vim/bundle since you don't use pathogen anymore)

  - >
    git cleanall -f
    emacs.d/vendor/
    irssi/scripts/vendor/
    jupyter/nbextensions/
    shell/plugins/
    vim/bundle/
    zsh/plugins/

Yeah, I think this removes submodules that were deleted on another machine, and then we git pulled on the current machine. And thanks for pointing out the vim/pack/vendor thing.

from dotfiles.