megabyte-labs / install.doctor

A glorious combination of application / theme settings and a performant cross-platform, desktop-oriented software suite.
https://megabyte.space
Other
99 stars 22 forks source link

`.viminfo` showing up in `$HOME` directory #47

Open ProfessorManhattan opened 1 year ago

ProfessorManhattan commented 1 year ago

❔ What are you experiencing an issue with?

Latest Release

❔ Version

Latest

🐞 Description

On macOS, the .viminfo is showing up in the user's home directory. This should be stored in the vim cache folder or wherever makes the most sense. Main point is to keep the $HOME directory clear of spammy dotfiles.

⏺️ Steps To Reproduce

No response

πŸ“’ Relevant Log Output

No response

πŸ’‘ Possible Solution

No response

ProfessorManhattan commented 1 year ago

Please also look into getting rid of the .docker/ folder.

enggnr commented 1 year ago

The fix for .viminfo location (set viminfo+=n~/.config/vim/viminfo) is available here already. Tested this and it works (the folder .config/vim should exists for the file to be saved there).

As for the ~/.docker folder, it appears to be installed during the installation of docker-pushrm plugin. This is documented in the source repository. This is one of the locations (appears to the first folder where plugins are searched per this. That link also shows the other locations (/usr/local/lib/docker/cli-plugins & /usr/local/libexec/docker/cli-plugins, /usr/lib/docker/cli-plugins & /usr/libexec/docker/cli-plugins), and this has some more info.

docker-pushrm plugin is installed using the Taskfile here. The source repository provides an alternate location to install which is one of the locations mentioned in the docker/cli issues. Do we want to update the Taskfile to install it in a system directory instead of $HOME?

enggnr commented 10 months ago

@ProfessorManhattan, this can be closed.