Prevent tree-sitter error on buffers that don't yet have a filetype #73
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.
Some debug adapters occasionally create a stack frame in a brand new buffer, e.g. if jumping into memory that requires disassembly. For some reason, there are rare cases where nvim-dap fires listener events on the new frame before Neovim has had the chance to determine the filetype. Since the filetype is empty, tree-sitter throws an error on
get_parser()
.This fix manually calls
vim.filetype.match()
on the buffer if the filetype is empty. If still empty, the function exits early.So, this fixes the rare edge case I was experiencing, as well as any potential case where Neovim cannot determine the filetype of the file being stepped into.