kylo252
kylo252
@mfussenegger, what do you think of this change? I'm a bit split on normalizing slashes in the final result, but I guess it's a requirement?
> Does this solve the same thing? #19988 it's orthogonal, that one is about keeping the backslashes when on unix (used for escaping, I guess?), see https://github.com/neovim/neovim/issues/19984
> This would break existing uses of `vim.lsp.start`. We shouldn't do that unless there is a _very_ good reason. It's definitely not my intent to break backwards compatibility for `vim.lsp.start`,...
> Hold up. This slows linting by 4 times, and that's with parallelization. Without any parallelization it takes 8 times as long. are you comparing these numbers locally or is...
> Those questions are irrelevant for this PR. > The question is whether ctest is worth running. If it's much slower then it obviously isn't. I think you're missing the...
> No, I'm talking specifically about > I compared the time to do `ctest --test-dir build -R 'lint' -j$(nproc) --progress` compared to `make lint` on `master`. could you test it...
> > Apologies if this is something that most neovim users would know, but could we add something to the documentation explaining how one would use this? (btw, this would...
fixed in #3127
Please let me know if you're still facing an issue with this.
This is an upstream issue unfortunately, I can reproduce this with a minimal config expand ```lua local on_windows = vim.loop.os_uname().version:match "Windows" local function join_paths(...) local path_sep = on_windows and "\\"...