-
-
Notifications
You must be signed in to change notification settings - Fork 632
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
TPM installation not working / installation causes conflicts in plugins directory (Consider renaming repository?) #129
Comments
tmux
causing conflicts (Consider renaming repository?)
tmux
causing conflicts (Consider renaming repository?)
Hi, I'm one of the core maintainers of Catppuccin 👋 From an organisation perspective, I'd like to avoid renaming this repository as it goes against our naming convention for applications that we support. We ran into a similar situation with our catppuccin/nvim repository, but the plugin managers for that ecosystem allowed plugins to be downloaded under a different name. In the other issues that have been raised, I can see that tpm itself has an issue and a PR that aims to "fix" this:
While waiting for tpm to (hopefully) allow overrides to plugin names, I can think of 2 immediate "workarounds":
Curious what others think! |
I tried forking it using new names from my repo as well as other people repo but it is still not working? what am I doing wrong? Here are the steps that I did:
After this, I did |
I tried using your repo, it worked for me. (I completely The last line seems to show that you installed |
When using this plugin, it creates a dir in the tmux plugs dir named
tmux
. This can potentially cause issues with other plugins namedtmux
in the same folder in the futureOther themes are named with a more unique name:
I recommend naming this git repo something like
tmux-catppuccin
instead oftmux
so that is it more unique and does not cause any naming clashes in the future.The text was updated successfully, but these errors were encountered: