You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am not sure if anybody else is experiencing issues in this regard.
If I use the ansi-term the shell seems quite buggy (I can not edit something within the line as the
cursor always jumps to the end). So finally I end up having everything in a buffer and sending the relevant
lines to the terminal. Also the history is borged etc.
I don't experience this behavior with vterm (If one could use multivterm it would be amazing but I guess
having multiple julia repl's running and sending code to each one individually is difficult to implement).
The problem is getting the vterm backend to run.
At startup the function 'julia-repl-set-terminal-backend' doesn't exist. Only after I visit a .jl file.
Is there a way in which I can set "vterm" as default terminal?
If I set vterm sometimes I can start the repl and it works other times I get "Expected vterm-mode. Changed mode or backends?" After that I can only switch back to "ansi-term" otherwise the repl doesn't fire up again.
After more testing it seems as if this happens when I first visit a julia file, fire up the terminal (with "ansi-term")
and then exit and set the backend to "vterm" afterwards.
I tried to look into the code but it is beyond me to understand it.
If somebody knows by chance I would also like to learn how the lsp recognizes the code because it
seems when I install new packages within the activated environment the lsp doesn't recognize
the newly imported functions, only upon restart of emacs it works.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
I am not sure if anybody else is experiencing issues in this regard.
If I use the ansi-term the shell seems quite buggy (I can not edit something within the line as the
cursor always jumps to the end). So finally I end up having everything in a buffer and sending the relevant
lines to the terminal. Also the history is borged etc.
I don't experience this behavior with vterm (If one could use multivterm it would be amazing but I guess
having multiple julia repl's running and sending code to each one individually is difficult to implement).
The problem is getting the vterm backend to run.
Is there a way in which I can set "vterm" as default terminal?
After more testing it seems as if this happens when I first visit a julia file, fire up the terminal (with "ansi-term")
and then exit and set the backend to "vterm" afterwards.
I tried to look into the code but it is beyond me to understand it.
If somebody knows by chance I would also like to learn how the lsp recognizes the code because it
seems when I install new packages within the activated environment the lsp doesn't recognize
the newly imported functions, only upon restart of emacs it works.
Beta Was this translation helpful? Give feedback.
All reactions