Generic (universal) LSP support without adapter #46

fzzr commented 2026年03月06日 12:39:35 +01:00

It could be absolutely awesome killer-feature if Gram support any LS via LSP with just single requirement — define it in the configuration. Without adapters, wrappers, etc.. Like it today works in Helix.

❤️‍🔥

It could be absolutely awesome killer-feature if Gram support __any LS__ via LSP with just single requirement — define it in the configuration. Without adapters, wrappers, etc.. Like it today works in Helix. ❤️‍🔥

fzzr commented 2026年03月13日 17:35:22 +01:00

I'll try to take it after my adventure with upstream-merge-hell.

I'll try to take it after my adventure with upstream-merge-hell.

fzzr commented 2026年03月20日 21:09:06 +01:00

Update. I could take this issue after someone pull latest LSP-features from upstream. (rel. issue)

Update. I could take this issue _after someone pull latest LSP-features_ from upstream. ([rel. issue](https://codeberg.org/GramEditor/gram/issues/94))

krig commented 2026年05月14日 23:03:00 +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.