-
Notifications
You must be signed in to change notification settings - Fork 3.5k
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
Terminal, impossible to type \ antislash #17057
Comments
This comment was marked as resolved.
This comment was marked as resolved.
Of course
Keyboard : azerty, french ( |
Potentially relevant: |
I am facing the same problem on MacOS. \ / | and all those keys stopped working within the terminal. Running some scripts which ask for user input are printing control chars/garbage into the input field (without typing anything) like: Project name (lala): ]11;rgb:3b3b/4141/4d4d Using: Zed 0.150.4 |
Same problem here with a French keyboard on a Mac, I can't type the |
Try to add in {
"terminal": {
"option_as_meta": false
}
} This solved my issue. See issue #17031 for details... |
Check for existing issues
Describe the bug / provide steps to reproduce it
Hello
I use Zed to prepare a postgresql course, and I use the terminal for many manipulations.
So I detected that I can't enter the
\
(antislash) character in the terminal, and I have to enter it in the editor and copy/paste it in terminal... Annoying to make a\q
for example ;-)If I am at the bash level (not in psql), successively pressing \ and \ makes an
ls
I've check
settings>key bindings
andsettings>default key bindings
I didn't detect anything suspect (I didn't change the default values)Of cours, i'ts possible to make a \ in the classic terminal, in the VSC terminal, and in other applications in general
Environment
MacBook Air
MacOS Sonoma 14.4.1 (23E224)
To obtain \ a need to use shift+option+/
If applicable, add mockups / screenshots to help explain present your vision of the feature
No response
If applicable, attach your Zed.log file to this issue.
Zed.log
The text was updated successfully, but these errors were encountered: