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

.viminfo showing up in $HOME directory #47

Open
ProfessorManhattan opened this issue Jun 1, 2023 · 3 comments
Open

.viminfo showing up in $HOME directory #47

ProfessorManhattan opened this issue Jun 1, 2023 · 3 comments
Assignees
Labels
bug Something isn't working

Comments

@ProfessorManhattan
Copy link
Contributor

❔ 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 ProfessorManhattan added the bug Something isn't working label Jun 1, 2023
@ProfessorManhattan
Copy link
Contributor Author

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

@enggnr
Copy link
Contributor

enggnr commented Jul 15, 2023

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
Copy link
Contributor

enggnr commented Nov 9, 2023

@ProfessorManhattan, this can be closed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants