Conrad Irwin
Conrad Irwin
For the multi-key case this turned out to be only broken if you had (at some point) opened a second zed window. For `
@rpfaeffle similar to the other one, it seems worth merging this as it improves javascript (which I think will remain "in-core" for a while). Would you mind rebasing on main...
@noritada Thanks for taking a pass at this! I agree the current situation is confusing. To summarize what you said, there are at least ~2 problems right now: 1. It's...
@bswinnerton Thank you so much for taking a pass at this, it's one of the big vim pain points right now. If you'd like to pair with me to get...
@bswinnerton let me know if you're still planning on taking a look at this; otherwise I'll put it back on my backlog
:+1: Closing this for now. Race you for who gets to it first :D.
Thanks for sharing, this is awesome! Any chance I could cajole you into making it work on macOS too??? I'm going to close this for now, but I hope we...
Our current plan is to move everything to an extension and then install some extensions by default. I'm not sure in this specific case: on the one hand having an...
It seemed clearer to me (`zed://channel/X`, `zed://file/{X}`, vs `zed://channel/X` being a channel and `zed:///channel/X` being a file) and is the same as VScode.