Using META key (Option) on Mac stops working on 'sudo su'

Open
#2,430 4 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
bash, macos, rust

Research direction

Start by reproducing the behavior on macOS 13.1 with bash 3.2.57, comparing normal input with a session entered through sudo su. Trace how Warp handles Option-B, Option-F, and Option-Backspace in the superuser session; done means these keys retain word-navigation and deletion behavior locally and remotely.

Written by the indexing model from the issue text.

Description

bug ready-to-implement triaged
Discord username (optional)

impulse

Describe the bug

I use META key with 'f' and 'b' keys to go forward and backward one word (standard emacs behavior I believe).

This works fine on the machine running Warp. Works fine when I log in to a remote server.

But, as soon as I switch to superuser, locally or remotely, I get these special characters printing out:
on Option-B: ∫
on Option-F: ƒ

Also, Option-Backspace deletes a single letter rather than the whole word.

To Reproduce

sudo su
press Option-B, Option-F, or Option-Backspace within multi-word line

Expected behaviour

described above

Screenshots

No response

Operating System

MacOS

OS Version

13.1

Shell Version

GNU bash, version 3.2.57(1)-release (arm64-apple-darwin22)

Warp Version

v0.2002.12.13.08.04.stable_01

Additional context

No response

Does this block you from using Warp daily?

Yes, this issue prevents me from using Warp daily.

Warp Internal (ignore): linear-label:b8107fdf-ba31-488d-b103-d271c89cac3e

None

Dominant language
Rust
Stars
65.1k
Forks
5.6k
PR merge metrics
PR metrics pending

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from warpdotdev/warp

All issues in warpdotdev/warp

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.