"Option key Meta" not working in `c3270` terminal application

[dankox]

Discord username (optional)

No response

Describe the bug

Using c3270 application on MacOS in warp and having "Option key Meta" enabled, doesn't really work. My key setup in the application doesn't work in warp.
In all the other terminal application it works without a problem, so it's definitely c3270 problem. I used kitty or even default terminal and it is fine there.

To reproduce

Add keymap in c3270 with Alt<Key> mapping and try to use it in the application. It will not be recognized.

Expected behavior

Application c3270 recognize the Alt<Key> mapping when meta is enabled on MacOS.

Screenshots

No response

Operating system

MacOS

Operating system and version

Ventura 13.5

Shell Version

zsh 5.9 (x86_64-apple-darwin22.0)

Current Warp version

v0.2024.01.16.16.31.stable_01

Regression

No, this bug or issue has existed throughout my experience using Warp

Recent working Warp date

No response

Additional context

I see other issues around which mention this kind of problem but are refering to emacs, or other apps. I'm not sure if the reason is because the c3270 is full terminal application and wrap then doesn't wrapify it meaning the settings doesn't apply to it. Or if it's something else.

Does this block you from using Warp daily?

No

Is this a Warp specific issue? (i.e. does it happen in Terminal, iTerm, Kitty, etc.)

Yes, this I confirmed this only happens in Warp, not other terminals.

Warp Internal (ignore): linear-label:b9d78064-c89e-4973-b153-5178a31ee54e

None

[sinefabula]

Seems like the issue is not specific to your application. I get the same behaviour with python and sqlite3 interpreters, e.g. when using Option+b and Option+f to navigate by words. I'm on fish but that also doesn't seem to be the issue because I've also tried those interpreters with zsh and bash, and it's the same: meta key works in Warp itself but breaks inside an interpreter.

[oz-by-warp]

We need a bit more information before we can continue triaging this issue.

If you're still hitting this, could you try reproducing it on the latest version of Warp and share logs along with a screenshot or short video if possible?

If there's no activity after 3 business days, we'll close this out to help keep the tracker tidy.

---

This is part of an automated backlog review and may be inaccurate. If you believe this assessment is wrong, please let us know.

[github-actions]

This issue has been automatically closed because it was labeled needs-info and received no response for 3 business days. If you have the requested information, please reply and we will reopen.