mattn

Results 918 comments of mattn

Hmm, I don't get it. ``` call lsp#callbag#pipe( \ lsp#callbag#fromList(l:servers), \ lsp#callbag#flatMap({server-> \ callbag#pipe( \ lsp#request(server, l:request) \ ) \ }), \ lsp#callbag#takeUntil(lsp#callbag#pipe( \ lsp#stream(), \ lsp#callbag#filter({x->has_key(x, 'command')}), \ )),...

@prabirshrestha Probably, the registered repository URL on opencollective is wrong. ![image](https://user-images.githubusercontent.com/10111/174259284-fc2f0656-e046-40e2-a3d2-c901c0735c88.png) currently it is https://github.com/prabirhrestha/vim-lsp it should be https://github.com/prabirshrestha/vim-lsp

Thank you. This problem is fixed by https://github.com/prabirshrestha/vim-lsp/pull/1340

I'm not an owner of this repository but I'd say this is not an issue of vim-lsc or vim-lsp. See https://github.com/prabirshrestha/vim-lsp/issues/816

I will add code for `v:shell_error`. About `maxfuncdepth`, job_status catch-up another running jobs. So when another job make the error, exception will be raised at the line at job_status. The...

yes, we have better to separate `s:system` and `s:systm_with_error`? as far as i see, `s:system` is used in many part like `let foo = s:some_func(s:system(cmd))`.

added `s:system_with_error` which return two values.

Sorry, It's difficult to read the test result for me.

Yes, I could not find the discuss. But I think there are meaning of discussing this on GitHub.