Replies: 1 comment 6 replies
-
It sounds like you're using the built-in sources.providers.path.enabled = function()
return not vim.tbl_contains({ 'typescript', 'typescriptreact', 'javascript', 'javascriptreact' }, vim.bo.filetype)
end Thanks for reporting that the |
Beta Was this translation helpful? Give feedback.
6 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I'm a bit unsure if this relates to some of the opened issues, specially #46 and #541. In order not to clutter the issues list, I rather ask around here.
I noticed today something funky with accepting items, specially around paths and the
vtsls
LSP server.vtsls
lets you define aimportModuleSpecifier
configuration to let the LSP figure out how to import modules. I haven't had any issues withnvim-cmp
so far:cmp-ext.mov
However,
blink
doesn't seem to respect this and just puts the.tsx
extension in there:blink-ext.mov
Moreover (and probably not just related to
vtsls
), accepting different sections of the path adds extra characters. For example, here withnvim-cmp
, accepting theui
section of the path just completes withui
:cmp-dir.mov
However,
blink
also puts an extra/
at the end:blink-dir.mov
Here's my
blink
config, in case there's something missing on my end:Beta Was this translation helpful? Give feedback.
All reactions