I suspect you may be operating in "Restricted mode," aka it doesn't know if it can trust the directory. In that mode, the main tools like Rust analyzer are quite restricted. All of your complaints should be resolved once Rust Analyzer/basedpyrite are up and running. I do think they should have a more obvious warning that the current directory is untrusted, right now the little green warning in the corner is way too u…
Nailed it! I will do some more experiments and report back.
You should edit your original comment since it was user-error not the app being inferior.
I hate to dismiss Zed for such a stupid reason, but I have tried to use Zed seriously many times and every time I stop because I can't get over the theme. I've tried basically every single theme I can find that is reasonably popular and they are all equally poor. VSCode and Cursor have vastly better default themes. Does anyone have any suggestions here? I would love to use Zed more.
Does it really not let you change the colors? Am very unhappy at the modern trend to allow only canned themes.
I really like Zed but it's most recent big changes to Git integration and Parallel Agents has forced me to disable both of those features as the way they work just didn't suit me and my workflow
Don't need to create an issue, both have had issues for them for 2 years. https://github.com/zed-industries/zed/issues/9057 https://github.com/zed-industries/zed/issues/12629
Sort of a recurring theme, I find. They have 600+ issues that have been open for over a year, was hoping they'd drive down the backlog a bit before declaring victory
Go look at any large project, they have 500+/1000+ issues and many are ancient. Chrome, Firefox, you name it. I wouldn't be surprised if many issues have even been solved or need new reproduction steps but there's a difficulty to triaging all the issues as well.
The only thing that bothers me about Zed is the theme. It's so bland it actually gives me reading difficulties. I'd be surprised if some of the color combinations don't pose an accessibility issue. Grey text on grey background is quite the choice.
I do agree that Zed's default themes aren't great. They look too 'plain' for my taste. Bit more contrast can't hurt either. BUT: It's very easy to just choose a different theme and there are plenty to choose from by now. It's even possible to make your own theme and they even have a first-party theme editor ( https://zed.dev/theme-builder ) which works great. They should maybe include some descriptions for each color…
Thank you for the tips. I didn't know it was possible to install other themes as extensions.
Well done. I've been using Zed pretty much full-time for about 6 months now, and am happy with the experience.
There are still a few things PyCharm does better (debugging, for one), but overall Zed is very good and I haven't used PyCharm in months.
I still use CC in the terminal instead of inside Zed, and lazygit for reviewing git changes and other git actions (though Zed now does a decent job of the basics).
> My code (which works fine) looks like an ocean of red when I view it with Zed, and turning all those warnings off is not trivial. Isn't it just the default configuration of whatever LSP zed defaults to for PHP? So you should be able to either configure the LSP to avoid that or disable the LSP server entirely.
Coming from Sublime, I'd never even heard of a Language Server when I first tried Zed. As I recall, disabling particular kinds of warnings required copy-pasting some pretty exotic incantations into my project config. All of it was poorly documented, and it felt like I was doing something nobody expected me to do. Instead, I should have been able to mouse over a particular warning and say "don't warn me again about th…
Well, PHPStorm (and the other JetBrains IDEs) does it this way. You can disable a certain "inspection" globally, per project, per file, per method or just for one occurence - the last three work by inserting annotations into the code. Then again, PHPStorm costs money (not just if you want AI assistance), and is based on (drum roll) Java technology (although JetBrains don't advertise this fact a lot nowadays).
Congrats! My daily driver is Zed developing on SSH remote servers on exe.dev. It's crazy to think of all the dev tools I've churned through over the last 18 months but these two feel sticky. Zed has everything I need in a unified pane. File editor, terminal, agents, SSH remotes. And it's fast and intuitive exe.dev is the first "dev container" I've ever *loved*. The remote sandbox means `dangerously-skip-permissions`…
I'm glad to hear the SSH remote editing is working well. A lot of the time I'm developing on a remote server using VSCode Remote-SSH. I mostly love it. But! It consumes a lot of memory. And not only that. At times it gets stuck in some infinite loop or such, and ends up consuming all memory on the machine, preventing all traffic. Takes a few minutes for the OS to finally kill it, so I can get back in. I'm pretty this…
Do you happen to use the AutoImport extension? rg subprocess explosion seems related.
Too bad they did not include better search UI into this release. When you search, Zed opens a new tab, which I hate. Sometimes I just want to have a quick glance at some code and close the search using escape. Telescope style search in vim, helix or JetBrains tools is so much better. https://github.com/zed-industries/zed/pull/46478
I know not much about Zed and I am curious, can such changes be implemented via extensions?