alexwforsythe / tmux-which-key Goto Github PK

Hi, would you be open to me contributing more default values to more of the options in plugin/build.py? If not, the (optional)s should probably be removed from the README, b.c. they're misleading at the moment.

The documentation states this should work with tmux >= 3.0. However, it does not work with tmux 3.0 because an unsupported argument in "setenv".

I was able to make it work by changing the line 135 in plugin/build.py from:

        return -h 'setenv {} "{}"'.format(self.name, self.value)

to

        return 'setenv {} "{}"'.format(self.name, self.value)

The option -hwas added to tmux in version 3.2. So, I suggest updating the documentation or removing the use of this option.

Hi, I really apreciate somebody else also working with tmux menus!
My perhaps slightly over engineered aproach is at jaclu/tmux-menus

Using yaml for menu design certainly makes for easy config!

However one thing I almost immeditally noticed, was that as I opened various menus to see what was in there, there was no going back, so adding a back or previous menu option would be a huge usability gain.

Anyhow pretty neat!

Awesome plugin! Appreciate the work to make key binds more accessible.

I am unable to install with Nix as it makes the plugin directory read-only. To remedy this I added some basic support for XDG directories to enable this plugin to be installed and used on immutable or declarative operating systems.

By default this would put he config in ~/.config/tmux/plugins/tmux-which-key and the generated init file in ~/.local/share/tmux/plugins/tmux-which-key.

I also added an example config for installing with Nix via Home Manager. The config can be fully managed via Nix in a declarative manor. The init file can then be written to a directory which is cleared every boot (immutable via temporary file system).

#1

I was confused for a while when first using this plugin because I was typing C-b (prefix) and expecting which-key to appear after a short delay, similar to which-key.nvim.

Eventually I realized that the configured "keybind" are intended to activate which-key itself, however it'd be great to also have an auto-display option.

If this is difficult or impossible, perhaps the README could be improved to more clearly explain usage?