As written on the tin this PR allows Vim channels to connect to Unix-domain sockets, much nicer than TCP for local tasks and possibly faster (?).
Open questions:
port argument is omitted in ch_info, is that better than returning a meaningless value (empty string or zero)?ch_info return any info about the kind of socket it's connected to (ipv4, ipv6, unix)?https://github.com/vim/vim/pull/10062
(7 files)
—
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.![]()
@LemonBoy pushed 1 commit.
—
View it on GitHub or unsubscribe.
You are receiving this because you are subscribed to this thread.![]()
No idea what's wrong with the CI, the python script and the test suite both work fine on my system.
—
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.![]()
Perhaps ch_info() can return port zero to indicate a unix-domain socket?
The hostname is already used for the path, that combination would make sense.
Otherwise the info should have "path" and omit hostname and port.
—
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.![]()
Tests are still failing.
—
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.![]()
The tests are ok now, the CI failure is unrelated as master is also red right now.
—
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.![]()
—
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.![]()