Conrad Irwin
Conrad Irwin
This looks like a crash we've been seeing with alacrity, the panic is on a background thread (number 46) running: * `std::sys_common::backtrace::__rust_begin_short_backtrace::` cc @mrnugget
This was fixed.
The right fix is probably to make sure vim mode isn't enabled inside the feedback modal (or to change how vim works to bind its actions to the editor instead...
Updates having spent a bit of time looking into this approach, and talking with @nathansobo and @maxbrunsfeld. It turns out the Redis idea is not quite trivial because we rely...
With https://github.com/zed-industries/zed/pull/7130, this is all done (Except the command to switch to staging easily).
This is something I'd love to build, if you'd like to work on it together please pick a time: https://calendly.com/conradirwin/pairing. Otherwise, the approach I was going to take was to...
Adding a note here to think about the "leader" key in this context
Yeah. I think we can use the existing `"context": "Editor && vim_mode == normal"` etc. support for differentiating the various different kinds of maps. As to the difference between `nmap`...
This will be fixed in zed 0.124. You can now do things like: ``` { "bindings": { "down": ["workspace::SendKeystrokes", "4 j"], "cmd-alt-c": ["workspace::SendKeystrokes", ": copy relative path enter"], // *NOTE...
You can bind l directly instead of using SendKeystrokes: ``` "l": ["vim::PushOperator", "Replace"], ``` the contexts are not documented that well. There’s some [here](https://zed.dev/docs/vim) under custom key bindings, and some...