Open DanielViberg opened 5 months ago
I assume you are referring to the 'useBufferCompletion' option. Do you have a sample file that shows the problem?
Can you try removing the \C
from line 335 in completion.vim (https://github.com/yegappan/lsp/blob/main/autoload/lsp/completion.vim#L335)?
I'm trying to replicate it, will post when i find a good example.
Try changing line 11, writing another number than 15px. This is without \C
<script setup>
</script>
<style scoped>
.drag-cont {
display: grid;
position: relative;
}
.list {
display: grid;
gap: 15px;
}
</style>
<template>
<div>
</div>
</template>
var lspOpts = {
autoHighlight: true,
omniComplete: true,
useBufferCompletion: true,
snippetSupport: true,
ultisnipsSupport: true,
showDiagWithVirtualText: true,
diagVirtualTextAlign: 'after',
showDiagOnStatusLine: true,
showInlayHints: true,
noNewlineInCompletion: true,
outlineOnRight: true,
ignoreMissingServer: true,
highlightDiagInline: true,
showDiagWithSign: false,
diagSignErrorText: "▶",
diagSignInfoText: "⏺",
diagSignHintText: "⏺",
diagSignWarningText: "⏹",
filterCompletionDuplicates: true,
}
It seems like removing \C prompts the second error.
With useBufferCompletion: true
VIM - Vi IMproved 9.1 (2024 Jan 02, compiled Mar 7 2024 15:56:47) Included patches: 1-155