maxbrunsfeld

7 ms·

1.
by maxbrunsfeld 5mo ago
Yes
2.
by maxbrunsfeld 5mo ago
In the new layout, the project panel and git panel are just moved to the right side, so that the agent panel could be on the left, and you could still view both at the same time.
3.
by maxbrunsfeld 10mo ago
Curious about the failure to detect FS changes made outside of Zed. Are you on Linux?
4.
by maxbrunsfeld 10mo ago
Agreed, we should support this!
5.
by maxbrunsfeld 1y ago
The Zed spirit is definitely to prefer a platform native solution. You're right that we may be able to get rid of our WGSL implementation, and instead use the HLSL one via SPIR-V. But also, at some point we plan to port Zed to run in a
6.
by maxbrunsfeld 1y ago
The fix shipped in Zed 0.185.12.
7.
by maxbrunsfeld 1y ago
Isaac, that email that you sent to us (long after your internship ended) when Wasmtime first landed support for the WASM Component model was actually very helpful! We were considering going down the path of embedding V8 and doing JS extensi
8.
by maxbrunsfeld 1y ago
You can still include Text Threads as context in the inline assist prompt with @thread "name of thread", or using the `+` button. And it should suggest the active text thread for you, so it's one click. Let us know if that is
9.
by maxbrunsfeld 1y ago
I believe this PR fixes the issue: https://github.com/zed-industries/zed/pull/30178 .
10.
by maxbrunsfeld 1y ago
Thanks for the information. We can reproduce this using Copilot Chat. We're fixing now. We'll let you know when the fix is out.
11.
by maxbrunsfeld 1y ago
Yeah, we plan to revisit the collaboration features; it was painful but we decided we needed to pause work on it while we built out some more highly-requested functionality. We still have big plans for improving team collaboration!
12.
by maxbrunsfeld 2y ago
Some things are just much faster in an editor. I used `git add -p` until very recently (basically, until we built this feature in Zed). If you're using `add -p` and you notice a problem that you want to fix before committing, you need
13.
by maxbrunsfeld 2y ago
Just to clarify, you can run as many LSPs in a given file type as you want. Common features like completions, diagnostics, and auto-formatting will multiplex to all of the LSPs. Admittedly, there are certain features that currently only use
14.
by maxbrunsfeld 2y ago
You can. This is fully supported.
15.
by maxbrunsfeld 2y ago
There are extensions for scheme and racket: - https://zed.dev/extensions?query=scheme - https://zed.dev/extensions?query=racket
16.
by maxbrunsfeld 2y ago
I had the same question. I would think that with rust’s Vec, no allocation would occur at steady state. Vec does not automatically resize when removing elements.
17.
by maxbrunsfeld 2y ago
As a point of clarification, the script does not edit your zshrc file, it just prints a suggested edit that you may want to make to that file in order to add zed to your PATH.
18.
Extensible Language Support in Zed(zed.dev)
14 points by maxbrunsfeld 2y ago|0 comments
19.
by maxbrunsfeld 2y ago
If this happens with Zed 0.129 or later, could you open an issue? We had a problem at one point where there was a delay in macOS verifying our app’s code signature because we weren’t attaching the code signature correctly.
20.
by maxbrunsfeld 2y ago
> It has created a culture in which checking in enormous generates files is common. You're not required to do that, and never have been. We're going to move the grammars away from checking the generated `parser.c` in, but early
21.
by maxbrunsfeld 2y ago
Did you open an issue for the segfault you got, on the Tree-sitter repo or the repo for the particular parser you were using? It's not really accurate to say that Tree-sitter segfaults constantly. The Tree-sitter CI performs randomized
22.
by maxbrunsfeld 4y ago
The moment that you open Zed for the first time, you see a welcome screen that offers telemetry opt-out. The editor will be open-source and cross-platform, but it takes time to build things.
23.
by maxbrunsfeld 4y ago
Thanks for pointing this out. Our whole terms-of-service is just standard boilerplate provided by our lawyers, but this part doesn't really apply to Zed. Obviously, there's no "content moderation" for project code that
24.
by maxbrunsfeld 4y ago
> WebRTC Right now, this is just used for the screen-sharing feature. > The binary is pretty big by itself It is. One major reasons is that we're shipping a "fat binary" (x86_64 and arm64 build in a single file). We did
25.
by maxbrunsfeld 4y ago
Our plan is for the core editor to be free and open-source. We'll charge money for our backend service that powers collaboration in Zed. We have ambitious plans to improve the way that people work together on code. So far, on that fron
26.
by maxbrunsfeld 4y ago
No. It's written in Rust, with a custom UI framework. More details in this blog post: https://zed.dev/blog/videogame
27.
by maxbrunsfeld 4y ago
Yeah, the plan is to open-source the editor itself before we release 1.0. We will probably keep some part of the collaboration system closed-source, so that we can build our business around that feature set. We have some work to do to decid
28.
by maxbrunsfeld 4y ago
What forms of keyboard navigation are you missing? We try to make sure everything is controllable from the keyboard.
29.
by maxbrunsfeld 4y ago
We went with CoreText on macOS because we wanted to make sure that text in Zed matched the look of other macOS apps. We'll probably end up using HarfBuzz for the Linux and Web versions, and possibly Windows too.
30.
by maxbrunsfeld 4y ago
Yes, we do plan to open-source GPUI, as well as the Zed editor itself. Right now, our plan is to keep certain collaborative features the editor as closed source, because we would like to build a business around those features. So before we

More ›