Fork me on GitHub
#vim
<
2017-07-26
>
jebberjeb13:07:46

@dominicm any further progress with it? I'm not sure if I could provide any insight but willing to try if you've got some instructions to recreate.

dominicm13:07:04

@jebberjeb I'll have a try later with a more minimal example.

dominicm13:07:57

I believe, but haven't confirmed, that it's just using JUDs in an uberjar'd environment

jebberjeb14:07:00

@dominicm interesting. You mentioned you needed UDS support?

dominicm14:07:45

that's the default connection mechanism on unixes afaik. otherwise users need special instruction on starting the connector. This way I can spawn it & pass along the var.

jebberjeb14:07:19

Your use case is for REPL work right? Not an actual plugin?

dominicm14:07:36

It will be an actual plugin.

jebberjeb14:07:14

The plugins I've made so far all use STDIO. What's the advantage of UDS?

dominicm16:07:45

oh, they can use stdio? That might make more sense then. Maybe the julia readme is wrong 😛

jebberjeb16:07:41

heh, well they can do any of the three: TCP socket, UDS or STDIO.

jebberjeb16:07:30

I think in the neovim-client api there is a connect or new function that has arity for all 3 strategies, but I'm not sure. I know that from a REPL, obviously you wouldn't want to use STDIO.

dominicm16:07:07

No, makes sense. You would want to attach to external instance.

dominicm16:07:11

okay, stdio it is