Replies: 13 comments 31 replies
-
Not sure if this is relevant: after enabling Obsidian completions for Blink, |
Beta Was this translation helpful? Give feedback.
-
can you give a bit more context? |
Beta Was this translation helpful? Give feedback.
-
Hi, thanks for the fork, and for keeping the plugin rolling. I've just migrated to the fork. But, as above, I am unable to get blink to work with my setup. sources.min_keyword_length = function()
return vim.bo.filetype == 'markdown' and 2 or 0
end And have disabled |
Beta Was this translation helpful? Give feedback.
-
@sghng Sorry this one fell out of my radar, is it working now? Also, try to copy the |
Beta Was this translation helpful? Give feedback.
-
try removing I have ran out of ideas on why it is not working now. as #52 suggests, completion source are not sustainable and prune to failure for us, so It will eventually just lsp completion for markdown buffers, it will surely work then. Before that, maybe one of you would like to just do some print debugging on your environment to track down the issue. |
Beta Was this translation helpful? Give feedback.
-
Also ran into this issue. It looks like this is due to an update to blink.cmp within the last 8 weeks (that is when my lockfile goes back to). Once I restored to my lockfile, blink completion worked again. No updates to Obsidian.nvim were made during that time according to Lazy. |
Beta Was this translation helpful? Give feedback.
-
look at the comment above, It could be blink's api change, for now recommend you two to add |
Beta Was this translation helpful? Give feedback.
-
@sghng @jakubdonovan @santoshkal let's try this again, this time:
|
Beta Was this translation helpful? Give feedback.
-
Can anyone share a screen recording or screenshot of what completions functioning actually look like? I assume that after typing |
Beta Was this translation helpful? Give feedback.
-
@sghng sorry for taking long to reply, I still don't have a definitive answer, but just some observations
|
Beta Was this translation helpful? Give feedback.
-
Sharing because maybe for someone that information will be useful. For me blink completions didn't work because I only had I checked comments in here. And though I don't feel like that could be the answer in this case. If you don't explicitly disable Note for devs of this plugin: Repro Init.luavim.env.LAZY_STDPATH = ".repro"
load(vim.fn.system "curl -s https://raw.githubusercontent.com/folke/lazy.nvim/main/bootstrap.lua")()
vim.fn.mkdir(".repro/vault", "p")
vim.o.conceallevel = 2
local plugins = {
{
"obsidian-nvim/obsidian.nvim",
opts = {
completion = {
blink = true,
},
workspaces = {
{
name = "test",
path = vim.fs.joinpath(vim.uv.cwd(), ".repro", "vault"),
},
},
},
},
{
'saghen/blink.compat',
lazy = true,
opts = {},
},
{
"saghen/blink.cmp",
opts = {
fuzzy = { implementation = "lua" },
keymap = {
preset = "default",
},
},
},
}
require("lazy.minit").repro { spec = plugins }
vim.cmd "checkhealth obsidian" |
Beta Was this translation helpful? Give feedback.
-
The completion now works for me! Today when I was checking |
Beta Was this translation helpful? Give feedback.
-
The note completion works now, but this warning is emitted when doing completion: ![]() |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Blink completion shows up in health check:
However, I still don't get completions when typing double brackets. I'm not sure if Obsidian source should show up in Blink:
Beta Was this translation helpful? Give feedback.
All reactions