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

Escape code passthrough #3954

Open
PartyWumpus opened this issue Jan 25, 2025 · 2 comments
Open

Escape code passthrough #3954

PartyWumpus opened this issue Jan 25, 2025 · 2 comments

Comments

@PartyWumpus
Copy link

PartyWumpus commented Jan 25, 2025

Afaict, escape sequence are always understood by zellij and handled by zellij. This means any escape sequence zellij does not support, but the terminal emulator does support can't be used. It would be nice if there was a (probably disabled by default) option to pass through escape codes wrapped in a specific sequence, like tmux's \ePtmux;...\e\\ (tmux(1)#allow-passthrough) or screen's \eP..\e\\ (screen#Control-Sequences)

I suppose there could be a plugin which makes zellij understand the tmux escape, but applications aren't going to be sending it because they don't think they're in tmux (unless the plugin also sets the TMUX environment variable), but I think that's a much poorer solution (also not sure if a plugin can do that).

Any plugin that implements a new sequence (\ePzellij;...\e\\ for example) is going to get probably no support at all because that's a niche on a niche.

@Andrew15-5
Copy link

This will unblock #2814 and make fixing it pretty trivial, AFAIK.

@PartyWumpus
Copy link
Author

PartyWumpus commented Jan 25, 2025

This will unblock #2814 and make fixing it pretty trivial, AFAIK.

Sort of... It would make unicode placements viable, but I imagine anything involving any other kind of placement would be weird, as the program is trying to use a "pane-relative" position, but it's going to instead get an absolute, window-relative position.

This is okay though, because the program has to opt-in to zellij passthrough in any situation, so the developer is aware of this. Long term it would still be better for proper support, like it does have for sixel so the rest of the protocol works.

I see someone else in that thread also suggested what I am suggesting here and here

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

2 participants