oberblastmeister

Could you explain what issues you encountered? I would also suggest you not work on a pull request yet because there are some large changes in plenary notably async await....

Thanks for explaining. If you want to work on a pr that adds a configuration variable to change the `neuron` executable path, I will accept it. For the paths we...

since we already use `popup.nvim` for telescope, can you use that implementation for the floating window so there is no code duplication.

I mean use the library that creates popups for telescope which is [popup.nvim](https://github.com/nvim-lua/popup.nvim), no need to create a telescope picker

To clarify, you are writing floating window code that can be replaced by using an existing implementation such as popup.nvim which creates floating windows and is also used for telescope....

can't you just do [`popup.create(...)`](https://github.com/nvim-lua/popup.nvim/blob/6f8f4cf35278956de1095b0d10701c6b579a2a57/lua/popup/init.lua#L33)?

Because `hGetBuf` needs a `Ptr`?

@sjakobi I would like to implement this. Should I create a new package, such as `prettyprinter-linear`, or should I directly add this to `prettyprinter`. Are we trying to keep dependencies...

#101 for more info

What should we do about async vs sync path functions? I remember you saying that we should prefix the sync ones with `sync_`. What are your thoughts?