Backport git split diff view #90

gbarr commented 2026年03月11日 09:37:55 +01:00

Zed has updated its git diff view to give the option of stacked or split diff views. Personally I prefer a split view. This would be a great addition to Gram if backported

Zed has updated its git diff view to give the option of stacked or split diff views. Personally I prefer a split view. This would be a great addition to Gram if backported

sparx commented 2026年03月12日 17:27:35 +01:00

It looks like the relevant code is mainly in crates/buffer_diff/src/buffer_diff.rs.

Nonexclusive list of commits:

• github.com/zed-industries/zed@8bf3b4fece
• github.com/zed-industries/zed@4177be4479

It looks like the relevant code is mainly in `crates/buffer_diff/src/buffer_diff.rs`. Nonexclusive list of commits: - https://github.com/zed-industries/zed/commit/8bf3b4fece0fe639be9db178b86571af3e9f68e8 - https://github.com/zed-industries/zed/commit/4177be447925dce7b93ff1c3521b06ff5b248c7b

krig commented 2026年05月14日 23:06:12 +02:00

Hello,

I've decided to go through and close issues that I don't intend to fix. If it's a feature request for something that I haven't planned to do, then I would encourage you as the reader to fix it yourself! It's open source, I'm guessing most people who are using a code editor are coders, and it's good for you to learn new things. I've come to realize that I can't fix WGPU issues on a particular piece of hardware for example. Whoever has that problem will have to solve it so they can verify that the fix actually works.

If it's a packaging thing, like providing packages for a particular OS, Linux distro or architecture, then all I can say is that I have tried and there just isn't enough time in my life to support everything people want. What I have done is hook up this repo to a Github mirror with actions enabled: https://github.com/GramEditor/gram. My suggestion to anyone who needs or wants a particular build is to make a PR that adds build support that way.

Hello, I've decided to go through and close issues that I don't intend to fix. If it's a feature request for something that I haven't planned to do, then I would encourage you as the reader to fix it yourself! It's open source, I'm guessing most people who are using a code editor are coders, and it's good for you to learn new things. I've come to realize that I can't fix WGPU issues on a particular piece of hardware for example. Whoever has that problem will have to solve it so they can verify that the fix actually works. If it's a packaging thing, like providing packages for a particular OS, Linux distro or architecture, then all I can say is that I have tried and there just isn't enough time in my life to support everything people want. What I _have_ done is hook up this repo to a Github mirror with actions enabled: https://github.com/GramEditor/gram. My suggestion to anyone who needs or wants a particular build is to make a PR that adds build support that way.