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
..
test_did_save_event.vader	Use one LSP connection per project	2018-08-24 13:16:58 +01:00
test_lsp_client_messages.vader	Add textDocument/typeDefinition for LSP (#2226)	2019-01-21 23:06:28 +00:00
test_lsp_command_formatting.vader	test/lsp: ensure linter name is set	2019-01-26 04:46:41 +00:00
test_lsp_connections.vader	Use one LSP connection per project	2018-08-24 13:16:58 +01:00
test_lsp_error_parsing.vader	Support strings in data field of error responses	2018-07-13 06:42:28 +02:00
test_lsp_root_detection.vader	Add additional ways to detect LSP project root	2019-01-26 04:46:41 +00:00
test_other_initialize_message_handling.vader	Merge pull request #2035 from jparise/lsp_config_callback	2018-10-31 16:24:11 +00:00
test_read_lsp_diagnostics.vader	Update tests	2019-01-21 18:36:52 +03:00
test_reset_lsp.vader	Add a command for stopping all LSP clients	2018-03-06 10:23:55 +00:00
test_update_config.vader	Only send LSP config updates when the dict changes	2018-10-31 08:42:42 -07:00