I'll fix test fail in later.

Thanks that is nice. But I'll move this after the Vim 9.2 release.
Can a few people try it out? I'd also think that we should have a very simple practical example for this in the help.

It is not clear from the docs how ch_listen({address} [, {options}]) differs from the already existing function ch_open({address} [, {options}])? See :h channel-address for possible values of address.

@chrisbra This is simple practice example working as HTTP file server.

https://gist.github.com/mattn/3e691419c37fe7ce501dc37e2a1bb545

Thanks.

ch_listen(address [, options]) - Listen on a socket and accept connections
Returns a channel representing the listening socket
Calls a callback function when a new client connects
Supports both IPv4 and Unix domain sockets
channel_listen_unix(path, callback) - Unix domain socket support

Why do we need channel_list_unix()? It looks like this is already supported via ch_listen() anyhow, no?

I wonder if this would help @yegappan lsp to support lsp servers without stdio, e.g. godot lsp server that works only over http?

Call tree is below. Should we rename channel_listen to channel_listen_tcp ?

f_ch_listen
  channel_listen_func
    channel_listen (TCP)
    channel_listen_unix (Unix Domain Socket)

I think we should have one single ch_listen() function, that accepts either a TCP address or a Unix domain socket, similar to ch_open(). I don't think we need separate vim script functions for tcp and unix domain sockets.

I wonder if this would help @yegappan lsp to support lsp servers without stdio, e.g. godot lsp server that works only over http?

@habamax This is already possible, see :h channel-address. You need to open a channel with ch_open() and then pass that channel to job_start() using its channel option (explained under :h job-options [below :h job-term] ). There's also an example in the docs under :h channel-demo using a Python server.

@chrisbra
The current implementation already follows this approach. ch_listen() accepts both TCP addresses and Unix domain sockets using the same pattern as ch_open():

• TCP: ch_listen('127.0.0.1:12345', ...)
• Unix socket: ch_listen('unix:/path/to/socket', ...)

The channel_listen_func() detects the unix: prefix and internally calls either channel_listen_unix() or channel_listen() accordingly. There is no separate ch_listen_tcp() or ch_listen_unix() function exposed to Vim script.

I think we should have one single ch_listen() function, that accepts either a TCP address or a Unix domain socket, similar to ch_open(). I don't think we need separate vim script functions for tcp and unix domain sockets.

ch_listen() is the only builtin Vim script function added, the others are implementation functions.