REPL instructions #128
Replies: 4 comments 2 replies
-
You shouldn't need to do that anymore. Just I have the functionality bound as so: (local repl-keys
[{:mods [:alt :cmd]
:key :r
:action (fn []
(alert "creating repl server")
(global repl-server (repl.start {:host "127.0.0.1"})))}
{:mods [:alt :cmd]
:key :s
:action (fn []
(alert "running repl server")
(repl.run repl-server))}
{:mods [:alt :cmd]
:key :t
:action (fn []
(alert "stopping repl server")
(repl.stop repl-server))}]) then ❯ fennel shevek.fnl localhost:7888
Connected.
>=> (+ 1 2)
3 |
Beta Was this translation helpful? Give feedback.
-
Oh cool. At first I was seeing some errors in the log, so I assumed it didn't work. Then I was able to connect to it using Monroe. It starts the REPL and I even tried typing |
Beta Was this translation helpful? Give feedback.
-
@agzam Nice! To do that open any fennel file and use @Grazfather Thinking about that connection issue. The auto-reloading was likely a stop-gap due to not having a REPL. Thinking of wrapping that feature in a state machine then maybe whenever a client connects to the REPL server it will disable auto-reloading until a disconnect or manual restart. |
Beta Was this translation helpful? Give feedback.
-
That's what I tried. But I can't seem to find a way to connect to the instance. Here's what I did:
|
Beta Was this translation helpful? Give feedback.
-
@Grazfather @eccentric-j Could please describe how to get it running? It's been quite a while since I touched any Lua related stuff. I naively thought that doing
luarock install jeejah
would magically work, but then I remembered how Jay has mentioned - currently, you have to manually edit the rockspec. Can you list the steps required, prior to:Beta Was this translation helpful? Give feedback.
All reactions