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

ANSI Escape sequences filtered, any reason for that? #2254

Closed
zokrezyl opened this issue Jun 2, 2020 · 5 comments
Closed

ANSI Escape sequences filtered, any reason for that? #2254

zokrezyl opened this issue Jun 2, 2020 · 5 comments

Comments

@zokrezyl
Copy link

zokrezyl commented Jun 2, 2020

Issue description

Tmux is filtering unknown escape sequences and that is making it unusable for the following purpose:

I was intending to use tmux on top of a new opengl terminal https://github.com/zokrezyl/asciterm . Asciterm is using libvterm for rendering text, but also is randering OpenGL shaders received as ANSI escape sequences.

My question is:

  • is there any trick to disable this filtering, and let tmux pass them to the underlying terminal or
  • would a patch that modifies the behavior be accepted

Required information

platform: Linux x86_64
tmux: 3.0a

@nicm
Copy link
Member

nicm commented Jun 2, 2020

You can use the DCS passthrough sequence to pass stuff, for example:

printf "\033Ptmux;abcdef\033\\"

You need to double any \033 in the sequence you want to pass.

@zokrezyl
Copy link
Author

zokrezyl commented Jun 2, 2020

Thanks for the quick answer. So the idea is in case environment variable TERM=tmux is defined, to send DCS pass through. Will test it and report back.

@nicm
Copy link
Member

nicm commented Jun 2, 2020

Better to check for TMUX than TERM.

@zokrezyl
Copy link
Author

zokrezyl commented Jun 2, 2020

Thanks for the advice. Can confirm the DSC pass through worked. Though I just bumped in other limitations I did not think about in my current design.

@github-actions
Copy link

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jun 10, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Development

No branches or pull requests

2 participants