Horacio Sanson

#3042 need someone to review or at least test it.

ALE tries to figure out the project root by looking for a compile_commnads.json file. If this is not found then it looks for .git/HEAD, configure, Makefile, CMakeLists.txt, and finally .git....

The concept of project_root is deep into ALE's internals for LSP. It is used in the intialize params message sent to the LSP for initialization (see [rootUri](https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#initializeParams)) so I am...

I am unable to find anywhere in ALE calling such function `ale#path#CdString`. Please try updating to latest ALE and try again.

You can see the *command* that ALE uses at [php.vim#L37](https://github.com/dense-analysis/ale/blob/master/ale_linters/php/php.vim#L37) ``` call ale#linter#Define('php', { \ 'name': 'php', \ 'executable': {b -> ale#Var(b, 'php_php_executable')}, \ 'output_stream': 'stdout', \ 'command': '%e -l...

This is because ALE is unable to find the root of the project when you create it inside GOPATH. When using go module the project contains a go.mod file that...

You can define a function that set flake8 and invokes ALELint and then call this function whenever you want. Somethink like this: ``` function RunFlake() let b:ale_linters = { 'python':...

Appreciated if anyone can verify #4160 solves this issue.

clangd is a language server so it requires a project root to be starterd. You can see what project root is being used by ALE by running this command: ```...

Maybe relevant information here: - https://github.com/clangd/clangd/issues/789#issuecomment-850132259 I do not use clangd so I am not sure what exactly should happen when invoking ALEGoToImplementation. From the discussion I linked it seems...