5 Commits

Author	SHA1	Message	Date
w0rp	cf270a1ada	Stop supporting ale_lsp_root ... We renamed the ale_lsp_root setting to ale_root long ago. Stop supporting the old setting name.	2023-09-16 17:17:42 +01:00
w0rp	680ba68d81	#3599 - Use ale_root instead of ale_lsp_root ... The `ale_lsp_root` setting is now deprecated, and `ale_root` should be used instead. The setting will be used for both setting the root easily for LSP linters, and for running other linters over whole projects.	2021-03-01 20:51:29 +00:00
w0rp	937138dad4	Try to fix the tests	2019-05-20 20:06:44 +01:00
w0rp	883978ece9	#2132 - Replace all uses of foo_callback with foo	2019-02-22 18:05:04 +00:00
brian m. carlson	6fc016ad05	Add additional ways to detect LSP project root ... Currently, we detect the linter root based on a variety of techniques. However, these techniques are not foolproof. For example, clangd works fine for many things without a compile_commands.json file, and Go projects may be built outside of the GOPATH to take advantage of Go 1.11's automatic module support. Add global and buffer-specific variables to allow the user to specify the root, either as a string or a funcref. Make the funcrefs accept the buffer number as an argument to make sure that they can function easily in an asynchronous environment. We define the global variable in the main plugin, since the LSP linter code is not loaded unless required, and we want the variable to be able to be read correctly by :ALEInfo regardless.	2019-01-26 04:46:41 +00:00