Addition of logger #6 - #383
Merged
Merged
Conversation
language server now expects to be run directly through language-server.js
…if something fails
the configuration supports overriding the default function as get_root_dir fixes zbirenbaum#371
the configuration supports overriding the default function as get_root_dir fixes zbirenbaum#371
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Addition of a new unit (logger.lua) to centralize the logging and the notify processes, including new configurations to trace and log messages from the LSP.
config:
From the Readme:
logger
When
log_to_fileis true, logs will be written to thefilefor anything offile_log_levelor higher.When
print_logis true, logs will be printed to NeoVim (usingnotify) for anything ofprint_log_levelor higher.File logging is done asynchronously to minimize performance impacts, however there is still some overhead.
Log levels used are the ones defined in
vim.log:trace_lspcan either beoff,messageswhich will output the LSP messages, orverbosewhich adds additonal information to the message.When
trace_lsp_progressis true, LSP progress messages will also be logged.Careful turning on all logging features as the log files may get very large over time, and are not pruned by the application.
Fixes #356