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

Tmux passthrough error when opts enabled in Lazyvim #254

Open
pchest opened this issue Nov 30, 2024 · 6 comments
Open

Tmux passthrough error when opts enabled in Lazyvim #254

pchest opened this issue Nov 30, 2024 · 6 comments

Comments

@pchest
Copy link

pchest commented Nov 30, 2024

Issue

When I have "opts = {}" enabled in Lazyvim, even with no specific options present, I encounter an error in tmux whenever I open a file. This is true even if I have set -g allow-passthrough on in my .tmux.conf file.

Replication

All options disabled

image.nvim configured with empty options

Error message

Error message when opening any file in tmux

System Info

OS: pop os 22.04
tmux version: 3.5
nvim version: 0.10.2

@b0o
Copy link
Contributor

b0o commented Dec 1, 2024

Did you reload your tmux config after setting the option?

@pchest
Copy link
Author

pchest commented Dec 3, 2024

@b0o Yes, I did. This error persists after refreshing the terminal or even a full system reboot. I also encountered it on another device with pop os 22.04 installed.

@skogler
Copy link

skogler commented Dec 3, 2024

@pchest I think this is related to tmux >= 3.3, I experimented a bit and changed the tmux option to:

set -pg allow-passthrough on

@pchest
Copy link
Author

pchest commented Dec 3, 2024

@skogler Strangely, that doesn't seem to resolve the issue. I changed my tmux.conf, but still got a similar error when image.nvim options are enabled.

.tmux.conf

image

Error message

image

@skogler
Copy link

skogler commented Dec 4, 2024

@pchest Ah, sorry, I think my tmux was not reloaded properly. I also got it again now on this boot.

Changing it to:

setw -g allow-passthrough on
set -g visual-activity off

Seems to have resolved it though, but not 100% sure if thats why I don't get the warning anymore now

@pchest
Copy link
Author

pchest commented Dec 11, 2024

Thanks for the reply! @skogler. Unfortunately, this change doesn't seem to do the trick either.

image

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

3 participants