You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Before filing, I have searched for similar issues.
Neovim Version
NVIM v0.11.0-dev-1369+gb03e790cdd
Multiplexer Integration
tmux
Multiplexer Version
tmux 3.5a
Steps to Reproduce
Create config for smart-splits.nvim
Open neovim and notice config is ignored at initialization
Expected Behavior
Config is respected
Actual Behavior
Config is ignored
Minimal Configuration to Reproduce
See additional details.
Additional Details and/or Screenshots
Currently increasing the log_level or disabling the multiplexer_integration is ignored during the initialization phase, as the user config is only loaded afterwards.
For example, this config
require('smart-splits').setup({
-- enable or disable the tmux Integrationmultiplexer_integration=false,
log_level='error',
cursor_follows_swapped_bufs=true,
})
Will not be respected on initial loading of neovim.
This causes issues where despite increasing the log_level and disabling the multiplexer_integration, I will still receive error messages based on the tmux integration (which I do not wish to use).
In my case, I use the following for quick editing of tmux scroll back buffer in neovim
However this will always trigger an annoying logging message since initially the config is ignored and tmux is initialized. Basically tmux init happens before config is loaded. Here is the sequence of event when loading the scrollback buffer:
Yeah, the idea is so that you don't necessarily need to call setup() . I'm potentially willing to revisit that, but I'll need to put more thought into it since it would be a breaking change.
Likely won't get to it till after christmas since I'm at my parents' house till then.
Similar Issues
Neovim Version
NVIM v0.11.0-dev-1369+gb03e790cdd
Multiplexer Integration
tmux
Multiplexer Version
tmux 3.5a
Steps to Reproduce
smart-splits.nvim
Expected Behavior
Config is respected
Actual Behavior
Config is ignored
Minimal Configuration to Reproduce
See additional details.
Additional Details and/or Screenshots
Currently increasing the
log_level
or disabling themultiplexer_integration
is ignored during the initialization phase, as the user config is only loaded afterwards.For example, this config
Will not be respected on initial loading of neovim.
This causes issues where despite increasing the
log_level
and disabling themultiplexer_integration
, I will still receive error messages based on the tmux integration (which I do not wish to use).In my case, I use the following for quick editing of tmux scroll back buffer in neovim
However this will always trigger an annoying logging message since initially the config is ignored and tmux is initialized. Basically tmux init happens before config is loaded. Here is the sequence of event when loading the scrollback buffer:
It would be great if the config can be respected and prevent tmux initialization and therefore error message.
The text was updated successfully, but these errors were encountered: