Closed awerebea closed 6 months ago
Hello @awerebea š
I initially didn't want to support configuring plugins with @tpm_plugins
as it's rather documented by TPM as "plan B" and Oh my tmux! doesn't rely on TPM to discover the lists of plugins.
That being said, I just added support for it in branch gh-706
. Can you please give it a try?
Hi @gpakosz!
Well, if this is no longer intended to work in the main (master) branch, no problem, I can switch to specifying plugins using @plugin
instead of @tpm_plugins
(as I already did in my current configuration as a workaround).
I just didn't find such a problem either in open or closed issues (I probably just missed it) and decided to highlight it in case it was an unknown bug.
BTW, thank you for your excellent work on this project!
Well I'll support both from now on. But I won't mention that one can set @tpm_plugins
in the .local
file template
https://github.com/gpakosz/.tmux/issues/706#issuecomment-1889134711
I just added support for it in branch
gh-706
. Can you please give it a try?
Just tried the gh-706
branch and it works flawlessly. Thank you!
TPM doesn't recognize plugins when they are defined in
tmux.conf.local
asset -g @tpm_plugins
variable.Commands to run
~/.tmux.conf.local
contents:Commands to run
~/.tmux.conf.local
contents:Commands to run
Thus, it is possible to specify each plugin separately using the
set -g @plugin
syntax, but it is not possible to specify them all at once usingset -g @tpm_plugins
.