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

Custom directory name per plugin #230

Open
L1Q opened this issue Sep 13, 2022 · 4 comments
Open

Custom directory name per plugin #230

L1Q opened this issue Sep 13, 2022 · 4 comments

Comments

@L1Q
Copy link

L1Q commented Sep 13, 2022

Context

Some plugins would name their repository not after the plugin, but after the app, notably catppuccin/tmux
Their install instructions recommend using tpm like this

set -g @plugin 'catppuccin/tmux'

This results in the following folder path ~/.tmux/plugins/tmux.
Not very descriptive and potentially even conflicting.

Git can already clone a repository into a custom target directory

git clone https://github.com/tmux-plugins/tmux-open.git ~/.tmux/plugins/open

Right now, tpm would not recognize the ~/.tmux/plugins/open as a valid tmux-open installation.

Suggestion

  • Add a form of syntax where custom directory name can be provided for a plugin
set -g @plugin 'catppuccin/tmux' 'catppuccin'
  • Allow tpm to search for the installed plugins in the custom directory, install, update and remove them accordingly.
@theutz
Copy link

theutz commented Sep 14, 2022

I just got bit by this, too! This would be lovely.

@FranklinYu
Copy link
Contributor

I think #217 will fix this issue (if merged).

@mebble
Copy link

mebble commented Feb 4, 2024

I got bit this! I wanted to switch from catppuccin/tmux to dracula/tmux but when I <prefix>+I, the dracula plugin just wouldn't get installed. Then I looked into ~/.config/tmux/plugins and found that the catpuccin theme was in the tmux folder. I deleted this folder and only then did dracula get installed, also at the tmux folder! So plugins are not namespaced by the github username; the repo names are essentially global.

@dammitjim
Copy link

@mebble thank you for leaving that comment, this fixed an issue I was having which I was pulling my hair out over

Would be fantastic if #217 could get merged

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants