summaryrefslogtreecommitdiff
path: root/test/python_fixtures/pipenv
diff options
context:
space:
mode:
authorHoracio Sanson <horacio@allm.net>2019-05-22 10:30:24 +0900
committerHoracio Sanson <horacio@allm.net>2019-05-22 10:30:24 +0900
commitb41836130c9977317ba3f3ebc61daf05fc34f0da (patch)
tree72c1de271d31a3780e7c6b1b7c422bf8c4537f44 /test/python_fixtures/pipenv
parent67d49c75a819aa4e7ded97785a1014ba18f06e5d (diff)
downloadale-b41836130c9977317ba3f3ebc61daf05fc34f0da.zip
Fix HandleLSPDiagnostics buffer match logic.
To find the buffer corresponding to URIs reported by LSP the HandleLSPDiagnostics() method uses the built-in bufnr() function. From the documentation we learn that the first parameter of bufnr() is an expression, not a path. EclipseLSP will report project wide errors (e.g. gradle errors) that are not related to any actual source file with an URI that corresponds to the project root folder, e.g: file:///home/username/Projects/gradle-simple This URI will match any open buffer of files within the project root hiearchy, thus project-wide errors appear as part of every file within the project, e.g: file:///home/username/Projects/gradle-simple/src/main/java/Hello.java To fix this, this MR adds '^' to the beginning and '$' at the end of the URI path to force an exact match. This is how is recommended in vim help (see :h bufname).
Diffstat (limited to 'test/python_fixtures/pipenv')
0 files changed, 0 insertions, 0 deletions