feature request - extend repl integration to other languages #36

mattly commented 2026年03月05日 20:11:45 +01:00

I'd like to start a discussion about what extending REPL support in Gram beyond the scant support in Zed would look like. I've worked in a lot of lisp languages, and many other languages which have repls, and find the lack of support for those frustrating.

There is a pretty good general extensible model for this kind of thing with SublimeREPL, which supports stdio repls; despite SublimeREPL not having been updated in 11 years, it was easy for me to configure it to run a Fennel REPL. I know people who use Clojure would love to integrate wiht nrepl.

I'd like to start a discussion about what extending REPL support in Gram beyond the [scant support](https://zed.dev/docs/repl) in Zed would look like. I've worked in a lot of lisp languages, and many other languages which have repls, and find the lack of support for those frustrating. There is a pretty good general extensible model for this kind of thing with [SublimeREPL](https://packagecontrol.io/packages/SublimeREPL), which supports stdio repls; despite SublimeREPL not having been updated in 11 years, it was easy for me to configure it to run a [Fennel](https://fennel-language) REPL. I know people who use Clojure would love to integrate wiht nrepl.

krig commented 2026年03月05日 20:20:22 +01:00

I would love to see better REPL support in Gram.

I would love to see better REPL support in Gram.

mattly commented 2026年03月05日 20:32:28 +01:00

cool – this is something I'd be happy to take on, though I'm currently juggling a lot of other projects. I've been learning Rust, but I'm not familiar with the Zed codebase at all, and so am not at the point where I could sketch out what a good implementation might look like.

What do you think would be a good first foray into this?

cool – this is something I'd be happy to take on, though I'm currently juggling a lot of other projects. I've been learning Rust, but I'm not familiar with the Zed codebase at all, and so am not at the point where I could sketch out what a good implementation might look like. What do you think would be a good first foray into this?

krig commented 2026年03月05日 23:31:44 +01:00

Awesome, thank you! And no pressure. I have a lot of other commitments as well.

There is some support for Jupyter notebooks in Gram, but I have not explored it beyond looking around in the code a bit. But my assumption is that it implements something like a REPL, in a way. So maybe that could be a good place to start looking.

Awesome, thank you! And no pressure. I have a lot of other commitments as well. There is some support for Jupyter notebooks in Gram, but I have not explored it beyond looking around in the code a bit. But my assumption is that it implements something like a REPL, in a way. So maybe that could be a good place to start looking.

krig commented 2026年03月06日 05:23:30 +01:00

Take a look at the crates/repl/ crate, that seems to be the main implementation of jupyter notebooks.

Take a look at the `crates/repl/` crate, that seems to be the main implementation of jupyter notebooks.

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