GramEditor/gram
39
986
Fork
You've already forked gram
88

Repl feature not working #365

Open
opened 2026年07月05日 16:47:45 +02:00 by dantai · 3 comments
Contributor
Copy link

Hello,

At this point in time the REPL feature in gram is not working - at least partially. I tested it with R (zed-r extension) (ark kernel) and Julia.
Whilst zed is properly showing the kernel sessions and buttons to interact with in the editor, gram is not able to find the kernel and show it in the session list and does not show the REPL + kernel selection menu in the editor.

gram version is 3.0.1.

How to reproduce:

  1. Install zed-R + ark kernel
  2. open any R script
  3. choose 'repl: refresh kernelspecs' in the action menu.
  4. choose 'repl: sessions' to see listed kernel sessions. -> No kernels listed

Expected behavior:
In zed: ark kernel should be found, listed and chooseable inside the editor after running 'refreshing kernelspec' command.

I did not test the repl feature with python yet, so I do not know if it maybe works there?

Idea: Might it be feasible to port the latest repl crate from zed towards gram ? I might try something like that though I fear that it will get very complicated (and my machine is a slow compiler :( ) Or is it better to debug...?

Thank you!

Hello, At this point in time the REPL feature in gram is not working - at least partially. I tested it with R (zed-r extension) (ark kernel) and Julia. Whilst zed is properly showing the kernel sessions and buttons to interact with in the editor, gram is not able to find the kernel and show it in the session list and does not show the REPL + kernel selection menu in the editor. gram version is 3.0.1. How to reproduce: 1. Install zed-R + ark kernel 2. open any R script 3. choose 'repl: refresh kernelspecs' in the action menu. 4. choose 'repl: sessions' to see listed kernel sessions. -> No kernels listed Expected behavior: In zed: ark kernel should be found, listed and chooseable inside the editor after running 'refreshing kernelspec' command. I did not test the repl feature with python yet, so I do not know if it maybe works there? Idea: Might it be feasible to port the latest repl crate from zed towards gram ? I might try something like that though I fear that it will get very complicated (and my machine is a slow compiler :( ) Or is it better to debug...? Thank you!
Contributor
Copy link

@dantai wrote in #365 (comment):

(and my machine is a slow compiler :( ) Or is it better to debug...?

Offtop, but I still don't get why just "text editor" compile longer than Firefox now... Debug compile about 7-10 minutes, but release... Even with Mold or Wild.

> genlop -t gram
app-editors/gram-1.2.1
 merge time: 1 hour, 6 minutes and 58 seconds.
app-editors/gram-3.0.1
 merge time: 1 hour, 36 minutes and 52 seconds.
> genlop -t firefox
www-client/firefox-152.0
 merge time: 38 minutes and 27 seconds.
www-client/firefox-152.0.3
 merge time: 45 minutes and 2 seconds.

@krig, any thoughts about cleaup/remove obsolete code or it's Rust/crates related? It's also ok to create new issue.

@dantai wrote in https://codeberg.org/GramEditor/gram/issues/365#issue-6124298: > (and my machine is a slow compiler :( ) Or is it better to debug...? Offtop, but I still don't get why just "text editor" compile longer than Firefox now... Debug compile about 7-10 minutes, but release... Even with [Mold](https://github.com/rui314/mold) or [Wild](https://github.com/wild-linker/wild). ```bash > genlop -t gram app-editors/gram-1.2.1 merge time: 1 hour, 6 minutes and 58 seconds. app-editors/gram-3.0.1 merge time: 1 hour, 36 minutes and 52 seconds. ``` ```bash > genlop -t firefox www-client/firefox-152.0 merge time: 38 minutes and 27 seconds. www-client/firefox-152.0.3 merge time: 45 minutes and 2 seconds. ``` @krig, any thoughts about cleaup/remove obsolete code or it's Rust/crates related? It's also ok to create new issue.
Owner
Copy link

@koru Yeah I don't really understand how it can be so big either. It's ridiculous. We've already stripped out a lot of stuff...

@koru Yeah I don't really understand how it can be so big either. It's ridiculous. We've already stripped out a lot of stuff...

@krig really glad you took the initiative to make this fork, hopefully the amount of deps can be drastically reduced as well

@krig really glad you took the initiative to make this fork, hopefully the amount of deps can be drastically reduced as well
Sign in to join this conversation.
main
main
test/wgpu-on-mac
test-ci/failing-test-mac
test/failing-test-mac
test/build-on-22-04
test/wgpu-present-mode-mailbox
v2.1
test/altgr-fix-again
test/2.0.0-rc1
test/linux-build
test/objc2
v1.2.1
3.0.1
3.0.0
2.2.0
2.1.2
2.1.1
2.1.0
2.0.0
1.2.1
1.2.0
1.1.0
1.0.0
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
4 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
GramEditor/gram#365
Reference in a new issue
GramEditor/gram
No description provided.
Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?