@snoe my clojure operators and objects work there, which usually cover most of my needs, otherwise I use a scratch buffer or similar.

@ingvij is it possible to expose the current buffer's namespace through acid right now? (like fireplace#ns())

acid_namespace is different I think; always user for me

👍, acid.nvim.path_to_ns

acid will use user whenever ns isn't specified, so it'll always make use of already required data.

a bit less than https://github.com/tpope/vim-fireplace/blob/master/plugin/fireplace.vim#L561 😮 the fireplace code was a bit too dense for me to port. Would it be worth exposing path_to_ns as a @neovim.function ?`

Well, it does a bunch more actually.. I'm ok with exposing that as a function, but why simply not import it?

I'm not using python

or maybe I'm missing something

I see.. Then it'll probably be trickier to implement a command or a handler, if that's the case

Not sure how it would work with callbacks from python.

@dominicm as of now, there is no proper way, but I can probably have a handler to call a vim function/command with the returning data from the repl.. That'd be pretty straightforward and would solve the problem for handlers

commands are just a quick way to bind a vim command to a functionality (that will ultimately be handled by a handler). That can surely be circumvented by wrapping a user command around AcidSendNrepl.

That should probably work as I think about it. I think. Can you register anonymous functions in node host as a callback?

not really, but I think maintaining state for message ids in flight and dispatching accordingly in a generic handle_message function would be doable

http://of-vim-and-vigor.blogspot.ca/2014/01/anonymous-functions-in-viml.html 😛

I think it's worth mentioning that acid will only call your handler for the correct message id

https://github.com/hkupty/acid.nvim/blob/master/rplugin/python3/acid/session.py#L83