[flagged]
One of the people working for one of their investors posts moderately controversial stuff on Twitter. Boycott them!!
This kind of nonsense really takes away from stuff that actually matters.
Zed 1.0
121–130 of 727 posts
Re: Zed 1.0
#122Earlier quoted context omitted.
> 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…
LSP is how all editors work today and its simplified everything so so much. you should figure them out
Re: Zed 1.0
#123Earlier quoted context omitted.
Yes - the Claude ACP is nice, as I like to have a view of the code while chatting. Using just the terminal for dense/long running work feels like a handicap imo. It would be great if it supported more commands though!
> It would be great if it supported more commands though! What does it not support? I want to try and figure out if its shortcomings in the ACP/Claude SDK or if it's just features that Zed has yet to support?
I feel like it doesn't support some of the commands that manage Claude itself so think `/mcp` `/plugins` etc. Most of the common ones are configured to work though from what I've seen but the ones that do more configuration of Claude seem to be blocked.
Re: Zed 1.0
#124[deleted]
Re: Zed 1.0
#125I'd love to see the Alacritty terminal backend swapped out with libghostty (or more likely libghostty-rs). The work Mitchell is doing with Ghostty and the approach Zed has taken seem super aligned. And Mitchell definitely seems to want to make Alacritty an easy target for conversion, he was just talking about being open to help support Warp with it: https://x.com/mitchellh/status/2049159764261925005
Looks like Mitchell said he's already on it https://x.com/mitchellh/status/2049514540505964549
Re: Zed 1.0
#126Over the years I’ve tried plenty of fast, "snappy" code editors, but always found myself returning to Sublime.
Zed is the first one that got me to actually migrate. It does a great job of staying out of your way. Search and replace works seamlessly across multiple files with regex, and the extremely fast editing experience feels immediately familiar if you’re coming from Sublime. Being open source also gives confidence in its long-term viability.
Kudos to the team building Zed.
Re: Zed 1.0
#127Earlier quoted context omitted.
> 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…
that does sound like a pretty nice ui idea to add to code actions (command + .), it already lets you one-click add an ignore comment iirc so probably not too hard to wire a global per-project option
however, i think LSP or integrated linters/typecheckers have been standard fare in editors for a while now (zed does seem to have a lot more set up by default, but i like the sane defaults most of the time). The "correct" solution would be to configure whatever lsp zed is running for the project the way you want, and reap the benefits even outside of zed. for php the tools are listed here: https://zed.dev/docs/languages/php the main one seems to be Phpactor and you should be able to configure it globally or per project https://phpactor.readthedocs.io/en/master/usage/configuratio...
but i understand the frustration, sometimes i try to navigate an ancient python codebase and it really is a sea of red
Re: Zed 1.0
#128Congrats! 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`…
Using Zed with ssh is an interesting idea. I spend a lot of time mosh/ssh to VPSs, then running 'emacs -nw' locally on the server. This is a great setup since I love Emacs, but I will give Zed/ssh a try. Thanks.
Re: Zed 1.0
#129Earlier quoted context omitted.
> 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…
Re: Zed 1.0
#130Here is a top-level comment for people who want to post the things they wish Zed had.
Request: please be sincere if you claim "the one thing that keeps me from using Zed is X" ... because let's face it, there is probably more than one thing. Editor ecosystems are complex beasts, and it is ok if people are slow to switch, but the "one thing" claims are rarely credible to me. Anyhow, such comments are rarely consistent with how human nature works. People find rationalizations, and that's fine. It would just be nice if people were a little more self-aware. Changing editors is harder for some people more than others.
My suggestion: if you want to make Zed better for your use case, please smart by explaining who you are as a developer, what you've used, what your expectations are. And be intellectually honest about the last time you've made a big change to your development workflow. End soapbox.