Closed ElCbo closed 5 days ago
This never happens on my end. BTW, I use MSVC toolchain.
I guess zed open with not found default keymap.json, in windows might be C:\Users\$USERNAME\AppData\Roaming\Zed
, you can check.
I guess zed open with not found default keymap.json, in windows might be
C:\Users\$USERNAME\AppData\Roaming\Zed
, you can check.
This is the content
// Zed keymap // // For information on binding keys, see the Zed // documentation: https://zed.dev/docs/key-bindings // // To see the default key bindings run `zed: Open Default Keymap` // from the command palette. [ { "context": "Workspace", "bindings": { // "shift shift": "file_finder::Toggle" } }, { "context": "Editor", "bindings": { // "j k": ["workspace::SendKeystrokes", "escape"] } } ]
you can try add this in keymap.json, then ctrl-shift-p
to ensure if this can enable command palette?
{
"context": "Workspace",
"bindings": {
"ctrl-shift-p": "command_palette::Toggle",
}
}
And you can read this, another person package zed with mingw, I'm not familiar with this.
No, it didn't work either. Pressing Ctrl-Shift-P does not do anything. Is it normal zed reporting this message?
I built v0.149.6 today with the command cargo run --release
using stable-x86_64-pc-windows-msvc
and ran into something like this issue.
With the editor active, only the character buttons work (including the modifier buttons, allowing all characters to be typed). The shortcuts and "functional" buttons like backspace do nothing at all.
With the terminal active, the "functional" buttons do work, so I can use delete or backspace in the terminal in addition to typing characters. But the shortcuts still do not work, so I cannot bring up the command palette there either.
Another odd thing, which I don't know if is related or not, is that if I open the command palette by the menu and type, it doesn't show any suggestions at all. So I am not able to reach anything like default settings or keybindings to see if they look okay.
Building it on another computer seemed to produce a working binary.
The broken binary is 968MB, built on a computer with MSYS2 installed. The working binary is 133MB, built on a computer without MSYS2 installed.
Both builds were executed from Git Bash.
Is there any way I can get an exact description of what is executed during the build on each computer, so I could compare them and see where the difference is?
Seems I might be mistaken, and the broken binary is actually built with the x86_64-pc-windows-gnu
toolchain.
I was fooled by the fact that rust-toolchain.toml
doesn't specify any target for Windows like it does for macOS and Linux, while it seems cargo still respects the version specified in the file. The result was for my computer was that it picked the x86_64-pc-windows-gnu
because that was the default host.
Seeing the x86_64-pc-windows-gnu
seemingly doesn't produce a working binary, I'd think it could be a good idea to add the x86_64-pc-windows-msvc
target to the rust-toolchain.toml
to avoid further confusion like this.
same here compile worked without a hitch!
am not using MSVC toolchain (as it doesnt work here)
Check for existing issues
Describe the bug / provide steps to reproduce it
I have a very strange behavior. I compiled zed using mingw1310_64 with
cargo run --release
The window opens and I see the Welcome to Zed! intro screen. I disabled vim mode, opened a new file and begin to write. If I hit backspace or delete, nothing happens. The character stay. Also Ctrl+s doesn't do anything.
Next test was to enable vim mode. Then I am in NORMAL mode, but can't enter INSERT mode via i or a I'm not even able to enter anything. Back to disabled vim mode yields the same behavior as before enabling vim mode.
On closing zed, it'll ask for a filename to save.
Environment
Opening the command palette using Ctrl+Shift+P doesn't work either. The backspace also doesn't work in command palette.
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