GitButler created huge problems for me twice - it automatically added files to commits, including one that contained secrets. Okay, I know I had to add them to .gitignore, but why didn't it prompt me to add the files? There were even logs and cache files, among other things.
For me it's.. okay it's my daily driver already, but I really really want extensions to be able to create their own UI elements in the buffer, like VSCode does. Basically GPUI for extensions.
This would unblock people to write their own Jupyter integration for example, or whatever else they want. There's load of cool stuff like Argus https://github.com/cognitive-engineering-lab/argus that rely on creating buffers with custom UI, and Flowistry https://github.com/willcrichton/flowistry that rely on graying out some code, and I want this stuff on Zed too
Has the team commented on this? Coming from Emacs, it seems insane to not implement an API to the UI. GPUI looks great too, it’d be a real shame if they opted to keep the extensibility limited to just LSP servers and whatnot.
A git worktree directory contains a .git that just references the original directory’s .git, and Zed doesn’t support this configuration. So, there just isn’t any representation of change tracking when working in a worktree directory.
Gotcha. Is there a request in for this? The team seems incredibly productive (I'm sometimes offered multiple updates per day), and my completely uninformed and naive take is that this probably wouldn't be too big of a lift, relative to the stuff I'm seeing them ship regularly.
Two things. First, some economists study stated versus revealed preferences. [1] The idea is to figure out what people do rather than what they say they will do.
Second, in the case of people making feature requests, it could be a net-societal-gain [2] if feature requesters made some kind of binding commitment. (See also the hold-up problem [3].) Perhaps a potential customer would commit to "if/when feature X gets added, I will commit to using the product for 2 hours." or "... I will spend $10 on the associated cloud services." (The question of what happens if the customer reneges also has to be agreed upon up front.)
Okay, so what kind of solution are you looking for here? VS Code uses a closed-source LSP server for its C# extension. Rider is it's own custom stuff, of course.
So...where does that leave the Zed team? If existing LSPs aren't good enough, that's not a Zed problem: they're building an editor, not LSPs for your favorite language.
