-
|
I'm using this config #109 for using sidekick.nvim with zellij (only using zellij with sidekick. I run LazyVim directly in WezTerm). Is it expected behavior that scrolling back in NORMAL mode of the Am I missing something in the zellij config? Is this out of the scope of sidekick.nvim? |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
|
The actual terminal scrollback of a multiplexer, is just the screen. The multiplexer itself manages scrolling. Without a multiplexer, the scrollback would be the actual scrollback. Although, some AI tools also manage their own scrollback and would have the same issue. For tmux, sidekick can do things much better. When you enter normal mode, instead of just showing the regular terminal mode (meaning only the lines that are vivisble), I fetch the full scrollback from tmux and show that in a new buffer. The whole thing is completely seamless, so from a user standpoint nothing has to be done. Zellij on the other hand is pretty terrible with respect to their API. There's a bunch of things I can't do with zellij. So I'd really recommend to use the tmux backend instead, since that will give much better results. |
Beta Was this translation helpful? Give feedback.
The actual terminal scrollback of a multiplexer, is just the screen. The multiplexer itself manages scrolling.
This is for sure super annoying.
So if you are in insert mode and you scroll, it's actually the mux that will render a new screen. The scrollback is still only the lines that are visible on the screen.
Without a multiplexer, the scrollback would be the actual scrollback. Although, some AI tools also manage their own scrollback and would have the same issue.
For tmux, sidekick can do things much better. When you enter normal mode, instead of just showing the regular terminal mode (meaning only the lines that are vivisble), I fetch the full scrollback from tmux and show that in a n…