Support blink.nvim Autocomplete #770

TZProgrammer · 2024-11-15T23:53:32Z

🚀 The feature, motivation and pitch

Currently obsidian.nvim does not work with blink.nvim, only with nvim-cmp. However, as blink is gaining popularity and becoming the default for many, compatibility between blink and obsidian would be very welcome.

Alternatives

No response

Additional context

No response

NickvanDyke · 2024-11-27T05:35:57Z

https://github.com/benlubas/cmp2lsp may do the trick in the meantime? I don't know what obsidian.nvim's source name would be though, nor if it's guaranteed to be exposed

codingluke · 2024-12-04T07:25:41Z

Especially, now that lazyvim has an extra for blink.nvim, I guess more and more will switch. There is also https://github.com/Saghen/blink.compat. It would be great to have an example in the docs how to configure it properly. 🤗

Edit:
I managed to get the sources to blink. however, there is always an error as obsidian.nvim wants to register itself to nvim_cmp.

return {
  { "saghen/blink.compat" },
  {
    "saghen/blink.cmp",
    dependencies = {
      { "epwalsh/obsidian.nvim" },
    },
    opts_extend = { "sources.completion.enabled_providers" },
    ---@module 'blink.cmp'
    ---@type blink.cmp.Config
    opts = {
      sources = {
        completion = {
          enabled_providers = {
            "lsp",
            "path",
            "snippets",
            "buffer",
            "obsidian",
            "obsidian_new",
            "obsidian_tags",
          },
        },
        providers = {
          obsidian = {
            name = "obsidian",
            module = "blink.compat.source",
          },
          obsidian_new = {
            name = "obsidian_new",
            module = "blink.compat.source",
          },
          obsidian_tags = {
            name = "obsidian_tags",
            module = "blink.compat.source",
          },
        },
      },
    },
  },
}

The error:

Error 08:40:08 msg_show.lua_error E5108: Error executing lua: vim/_editor.lua:0: nvim_exec2()..BufEnter Autocommands for "*.md": Vim(append):Error executing lua callback: ...ocal/share/nvim/lazy/obsidian.nvim/lua/obsidian/init.lua:151: attempt to call field 'get_config' (a nil value)

I guess https://github.com/epwalsh/obsidian.nvim/blob/main/lua/obsidian/init.lua#L143-L158 this block should be guarded.

NickvanDyke · 2024-12-04T15:23:07Z

I got autocomplete for links at least (not sure what else obsidian.nvim might provide) using the marksman language server

sadtab · 2024-12-07T20:15:22Z

The permanent solution would be a LSP, not support for any given completion, cpm and blinks comes and goes. For example Neorg has its own mini LSP, you wont need to configure cmp for it

nvim-neorg/neorg#1603 (comment)

Alan-TheGentleman · 2024-12-13T18:54:01Z

LazyVim last update removed nvim-cmp in favor of blink-cmd. It would be great to see Obsidian.nvim support it !

sadtab · 2024-12-13T20:28:09Z

The permanent solution would be a LSP, not support for any given completion, cpm and blinks comes and goes. For example Neorg has its own mini LSP, you wont need to configure cmp for it

nvim-neorg/neorg#1603 (comment)

Actually I take this back, I say obsidian notes are markdowns anyway, and we already have markdown LSP, so we don't need to reinvent the wheel, the mentioned LSP already supports document linking auto complete, tag auto complete, insert TOC, tree sitter highlights are also available, other functionality like toggle checkboxs etc. actually I disabled the obsidian plugin entirely and I could do almost my daily workflow on my vaults.

In my humble opinion, the easiest, still most maintainable and extendable breakthrough, is to keep obsidian plugin, only related to obsidian specific functionalities like managing the vaults, referencing the tags/files (BY USING THE MD LSP, again not reinventing the wheel), front matter, opening the MD in obsidian etc.

Managing the highlights, auto complete anything, toggle the checkbox etc are done more maturely in markdown lsp

paulwyszynski · 2024-12-15T15:44:19Z

LazyVim last update removed nvim-cmp in favor of blink-cmd. It would be great to see Obsidian.nvim support it !

Yep, would be awesome! My workaround is to enable nvim-cmp again in the extras.

epwalsh/obsidian.nvim#770

yuchenfei · 2024-12-20T16:15:09Z

return {
  {
    "epwalsh/obsidian.nvim",
    dependencies = {
      "nvim-lua/plenary.nvim",
    },
    opts = {
      completion = {
        nvim_cmp = false,  -- disable!
      },
    },
    config = function(_, opts)
      require("obsidian").setup(opts)

      -- HACK: fix error, disable completion.nvim_cmp option, manually register sources
      local cmp = require("cmp")
      cmp.register_source("obsidian", require("cmp_obsidian").new())
      cmp.register_source("obsidian_new", require("cmp_obsidian_new").new())
      cmp.register_source("obsidian_tags", require("cmp_obsidian_tags").new())
    end,
  },
  {
    "saghen/blink.cmp",
    dependencies = { "saghen/blink.compat" },
    opts = {
      sources = {
        default = { "obsidian", "obsidian_new", "obsidian_tags" },
        providers = {
          obsidian = {
            name = "obsidian",
            module = "blink.compat.source",
          },
          obsidian_new = {
            name = "obsidian_new",
            module = "blink.compat.source",
          },
          obsidian_tags = {
            name = "obsidian_tags",
            module = "blink.compat.source",
          },
        },
      },
    },
  },
}

Muizzyranking · 2024-12-21T06:47:07Z

@yuchenfei doesn't this still require nvim cmp to be installed?

sebszyller · 2024-12-21T07:08:51Z

@yuchenfei doesn't this still require nvim cmp to be installed?

It does. You're registering obsidian sources with cmp and then using them in blink. It's a workaround not a replacement right now.

yuchenfei · 2024-12-21T07:22:51Z

@yuchenfei doesn't this still require nvim cmp to be installed?

Yes, it still requires nvim-cmp, but it only loads when completing in Obsidian notes. This is a workaround configuration to make it work for now.

Muizzyranking · 2024-12-22T11:03:19Z

Oh, thank you. I initially did that without registering the source. I'll do this.

stefanboca · 2024-12-22T19:34:48Z

@yuchenfei @sebszyller @Muizzyranking author of blink.compat here. FYI, when using blink.compat, nvim-cmp should not be installed. blink.compat mirrors the cmp api, including the cmp.register_source function you are using. I'll take a look at adding the cmp.get_config function as well so that this works out of the box.

shivayan-bora · 2024-12-23T09:34:15Z

I have been using the same above change mentioned by @yuchenfei and I am not sure if I am doing something wrong. I keep getting this error: failed to get completions with error: ...share/nvim/lazy/blink.compat/lua/blink/compat/source.lua:87: attempt to index local 'item' (a boolean value)

Here's my obsidian lua configuration:

return {
  {
    "epwalsh/obsidian.nvim",
    version = "*",
    lazy = false,
    ft = "markdown",
    dependencies = {
      "nvim-lua/plenary.nvim",
    },
    opts = {
      workspaces = {
        {
          name = "wiki",
          path = "/Users/shivayanbora/PKM/My-Wiki-Vault",
        },
      },
      new_notes_location = "notes_subdir",
      notes_subdir = "0_inbox",
      note_frontmatter_func = function(note)
        -- Add the title of the note as an alias.
        if note.title then
          note:add_alias(note.title)
        end

        local out = {
          id = note.id,
          aliases = note.aliases,
          tags = note.tags,
        }

        -- `note.metadata` contains any manually added fields in the frontmatter.
        -- So here we just make sure those fields are kept in the frontmatter.
        if note.metadata ~= nil and not vim.tbl_isempty(note.metadata) then
          for k, v in pairs(note.metadata) do
            out[k] = v
          end
        end

        return out
      end,
      -- Optional, customize how note IDs are generated given an optional title.
      ---@param title string|?
      ---@return string
      note_id_func = function(title)
        -- Create note IDs in a Zettelkasten format with a timestamp and a suffix.
        -- In this case a note with the title 'My new note' will be given an ID that looks
        -- like '1657296016-my-new-note', and therefore the file name '1657296016-my-new-note.md'
        local suffix = ""
        if title ~= nil then
          -- If title is given, transform it into valid file name.
          suffix = title:gsub(" ", "-"):gsub("[^A-Za-z0-9-]", ""):lower()
        else
          -- If title is nil, just add 4 random uppercase letters to the suffix.
          for _ = 1, 4 do
            suffix = suffix .. string.char(math.random(65, 90))
          end
        end
        return tostring(os.time()) .. "-" .. suffix
      end,

      -- Optional, customize how note file names are generated given the ID, target directory, and title.
      ---@param spec { id: string, dir: obsidian.Path, title: string|? }
      ---@return string|obsidian.Path The full path to the new note.
      note_path_func = function(spec)
        -- This is equivalent to the default behavior.
        local path = spec.dir / tostring(spec.id)
        return path:with_suffix(".md")
      end,
      templates = {
        folder = "templates",
        date_format = "%Y-%m-%d",
        time_format = "%H:%M:%S",
      },
      completion = {
        nvim_cmp = false,
        min_chars = 2,
      },
      ui = {
        enable = false,
      },
    },
    config = function(_, opts)
      require("obsidian").setup(opts)
      local cmp = require("cmp")
      cmp.register_source("obsidian", require("cmp_obsidian").new())
      cmp.register_source("obsidian_new", require("cmp_obsidian_new").new())
      cmp.register_source("obsidian_tags", require("cmp_obsidian_tags").new())
    end,
  },
  {
    "saghen/blink.cmp",
    dependencies = { "saghen/blink.compat" },
    opts = {
      sources = {
        default = { "obsidian", "obsidian_new", "obsidian_tags" },
        providers = {
          obsidian = {
            name = "obsidian",
            module = "blink.compat.source",
          },
          obsidian_new = {
            name = "obsidian_new",
            module = "blink.compat.source",
          },
          obsidian_tags = {
            name = "obsidian_tags",
            module = "blink.compat.source",
          },
        },
      },
    },
  },
}

paulwyszynski · 2024-12-23T12:38:07Z

@stefanboca could you post a config here to make it work with obsidian or maybe mention it in the blink readme? 😬

CaeChao · 2024-12-23T17:52:48Z

I have been using the same above change mentioned by @yuchenfei and I am not sure if I am doing something wrong. I keep getting this error: failed to get completions with error: ...share/nvim/lazy/blink.compat/lua/blink/compat/source.lua:87: attempt to index local 'item' (a boolean value)

Just switch the blink.compat to main branch

shivayan-bora · 2024-12-24T06:01:20Z

@CaeChao Am I doing this correctly? Sorry I am quite new to Neovim.

return {
  {
    "epwalsh/obsidian.nvim",
    version = "*",
    lazy = false,
    ft = "markdown",
    dependencies = {
      "nvim-lua/plenary.nvim",
    },
    opts = {
      workspaces = {
        {
          name = "wiki",
          path = "/Users/shivayanbora/PKM/My-Wiki-Vault",
        },
      },
      new_notes_location = "notes_subdir",
      notes_subdir = "0_inbox",
      note_frontmatter_func = function(note)
        -- Add the title of the note as an alias.
        if note.title then
          note:add_alias(note.title)
        end

        local out = {
          id = note.id,
          aliases = note.aliases,
          tags = note.tags,
        }

        -- `note.metadata` contains any manually added fields in the frontmatter.
        -- So here we just make sure those fields are kept in the frontmatter.
        if note.metadata ~= nil and not vim.tbl_isempty(note.metadata) then
          for k, v in pairs(note.metadata) do
            out[k] = v
          end
        end

        return out
      end,
      -- Optional, customize how note IDs are generated given an optional title.
      ---@param title string|?
      ---@return string
      note_id_func = function(title)
        -- Create note IDs in a Zettelkasten format with a timestamp and a suffix.
        -- In this case a note with the title 'My new note' will be given an ID that looks
        -- like '1657296016-my-new-note', and therefore the file name '1657296016-my-new-note.md'
        local suffix = ""
        if title ~= nil then
          -- If title is given, transform it into valid file name.
          suffix = title:gsub(" ", "-"):gsub("[^A-Za-z0-9-]", ""):lower()
        else
          -- If title is nil, just add 4 random uppercase letters to the suffix.
          for _ = 1, 4 do
            suffix = suffix .. string.char(math.random(65, 90))
          end
        end
        return tostring(os.time()) .. "-" .. suffix
      end,

      -- Optional, customize how note file names are generated given the ID, target directory, and title.
      ---@param spec { id: string, dir: obsidian.Path, title: string|? }
      ---@return string|obsidian.Path The full path to the new note.
      note_path_func = function(spec)
        -- This is equivalent to the default behavior.
        local path = spec.dir / tostring(spec.id)
        return path:with_suffix(".md")
      end,
      templates = {
        folder = "templates",
        date_format = "%Y-%m-%d",
        time_format = "%H:%M:%S",
      },
      completion = {
        nvim_cmp = false,
        min_chars = 2,
      },
      ui = {
        enable = false,
      },
    },
    config = function(_, opts)
      require("obsidian").setup(opts)
      local cmp = require("cmp")
      cmp.register_source("obsidian", require("cmp_obsidian").new())
      cmp.register_source("obsidian_new", require("cmp_obsidian_new").new())
      cmp.register_source("obsidian_tags", require("cmp_obsidian_tags").new())
    end,
  },
  {
    "saghen/blink.cmp",
    dependencies = {
      { "saghen/blink.compat", branch = "main" },
    },
    opts = {
      sources = {
        default = { "obsidian", "obsidian_new", "obsidian_tags" },
        providers = {
          obsidian = {
            name = "obsidian",
            module = "blink.compat.source",
          },
          obsidian_new = {
            name = "obsidian_new",
            module = "blink.compat.source",
          },
          obsidian_tags = {
            name = "obsidian_tags",
            module = "blink.compat.source",
          },
        },
      },
    },
  },
}

If yes, I am still getting the error: failed to get completions with error: ...share/nvim/lazy/blink.compat/lua/blink/compat/source.lua:87: attempt to index local 'item' (a boolean value)

Just for context:

UPDATE:

I deleted ~/.local/share/nvim and ~/.local/state/nvim and reinstalled everything. Still the same issue.

Muizzyranking · 2024-12-24T06:28:14Z

@shivayan-bora remove the part where you registered the source with CMP, blink compat's author said it wasn't necessary.

brianrodri · 2024-12-24T15:21:12Z

@shivayan-bora I believe you also need version = "*" for the saghen/blink.compat plugin until #770 (comment) is released.

CaeChao · 2024-12-24T18:23:31Z

@shivayan-bora my guess is that you are using LazyVim, so you need to put version = false inside { "saghen/blink.compat", lazy = true, version = false } to override the default setting from LazyVIm
or set vim.g.lazyvim_blink_main = true in your options.lua file
or you can just wait for the next release....

@Muizzyranking I think you still need the registered part above to make it work, blink.compat just mirror the CMP module, obsidian need to call the api in order to register the sources

Alan-TheGentleman · 2024-12-24T19:58:36Z

It's working perfectly for me with this configuration:

https://github.com/Gentleman-Programming/Gentleman.Dots/blob/main/GentlemanNvim/nvim/lua/plugins/obsidian.lua

Muizzyranking · 2024-12-24T22:06:54Z

@CaeChao blink.compat author said it wasn't neccessary.

@Alan-TheGentleman this is very similar to what I have too.

celfred · 2024-12-27T12:54:52Z

Well, I've tried to follow all pieces of advice, but it doesn't work on my side… No more completion with my LazyVim config. I had to set nvim-cpm to false :(

I guess I'll wait for the next obsidian.nvim version and I hope it will be able to auto-detect the config (for newbies like me !) when nvim-cmp is set to true.

Muizzyranking · 2024-12-27T13:10:21Z

@celfred can you share a snippet of what you did? Because for LazyVim, there is a custom spec to pass in custom sources as a list so you won't have to add the module, look at this extra for example. I am not with my pc at the moment but if I see your config, I could help you write LazyVim compatible config.

celfred · 2024-12-27T13:31:48Z

Thanks @Muizzyranking for this quick reply.
I'm not sure how your link can help me… sorry…

What I've done so far :

I added this at the end of my 'opts= {} ' in my obsidian.nvim file (in my plugins directory) :
`
config = function(_, opts)
require("obsidian").setup(opts)

-- HACK: fix error, disable completion.nvim_cmp option, manually register sources
local cmp = require("cmp")
cmp.register_source("obsidian", require("cmp_obsidian").new())
cmp.register_source("obsidian_new", require("cmp_obsidian_new").new())
cmp.register_source("obsidian_tags", require("cmp_obsidian_tags").new())
end,
`
I added this right after my 'opts={}' block :
{ "saghen/blink.cmp", dependencies = { "saghen/blink.compat" }, opts = { sources = { default = { "obsidian", "obsidian_new", "obsidian_tags" }, providers = { obsidian = { name = "obsidian", module = "blink.compat.source", }, obsidian_new = { name = "obsidian_new", module = "blink.compat.source", }, obsidian_tags = { name = "obsidian_tags", module = "blink.compat.source", }, }, }, }, },
I added this line in my 'config > options.lua' file :
vim.g.lazyvim_blink_main = true

Don't know if that explains anything… But thanks for your time !

rbmarliere · 2024-12-27T13:40:39Z

@celfred As a workaround I suggest you use marskman LSP.

celfred · 2024-12-27T13:46:33Z

@celfred As a workaround I suggest you use marskman LSP.

Well, I've read that suggestion too earlier, but I had no idea how to set up marksman LSP instead of what I'm using right now…

Muizzyranking · 2024-12-27T23:45:15Z

@celfred I just got hold of my PC, first of all remove the hack to register source in obsidian with cmp, blink compat has it covered

for blink
you can do this

{
    "saghen/blink.cmp",
    dependencies = {
      { "epwalsh/obsidian.nvim", "saghen/blink.compat" },
    },
    opts = {
      sources = {
        -- LazyVim as custom option copmpat to pass in external sources with blink.compat
        compat = { "obsidian", "obsidian_new", "obsidian_tags" },
        -- Optional to set kind name., not really neccesary.
        -- providers = {
        --   obsidian = {
        --     kind = "Obsidian",
        --     async = true,
        --   },
        --   obsidian_new = {
        --     kind = "Obsidian",
        --     async = true,
        --   },
        --   obsidian_tags = {
        --     kind = "Obsidian",
        --     async = true,
        --   },
        -- },
      },
    },
  }

To setup marksman lsp in lazyvim, go to your lazy.lua file and add this to the spec table.

{ import = "lazyvim.plugins.extras.lang.markdown" },

I will suggest you read LazyVim docs on how to extend/override plugins opts and importing extras. You might also need to peek the source code to get a better understanding.

ericsunplus · 2025-01-17T16:49:13Z

@ericsunplus i think you need to have a markdown lsp. My config is very similar to yours and it works for me.

Hi @Muizzyranking , I just install and configure the marksman LSP. Now [[ can trigger the selection, but # still not. Is this the same on your side? What is the markdown lsp you are using?

ericsunplus · 2025-01-17T17:00:12Z

I have continue to insert valid characters before the selection comes up.

I think it might be due to completion.min_chars of obsidian.nvim

Hi @rbmarliere , I try set min_chars to 1 or 0, both still not taking effect

Muizzyranking · 2025-01-17T23:21:48Z

@ericsunplus I generally don't expect completion from typing # because it's a header marker. I can't really help with that.

ericsunplus · 2025-01-18T03:33:16Z

@ericsunplus I generally don't expect completion from typing # because it's a header marker. I can't really help with that.

In the README doc of this obsidian plugin, it indicate that

Completion: Ultra-fast, asynchronous autocompletion for note references and tags via nvim-cmp (triggered by typing [[ for wiki links, [ for markdown links, or # for tags)

So # for tags is also something I want to achieve.

Thank you for the help anyway

patricorgi · 2025-02-11T04:26:07Z

This commit breaks the workaround above. Saghen/blink.compat@988fa19

stefanboca · 2025-02-11T04:29:16Z

@patricorgi could you explain how that commit breaks the workaround for you? At most it should remove the documentation field, and completion should work otherwise normally.

patricorgi · 2025-02-11T04:41:06Z

@patricorgi could you explain how that commit breaks the workaround for you? At most it should remove the documentation field, and completion should work otherwise normally.

Hi @stefanboca , thanks for the swift reply. I'm no expert to lua, so apologies in advance if I'm not delivering the most meaningful message below

With blink.compat installed with following

    { 'saghen/blink.compat', lazy = true, version = false },

I got the following error when editing a file in obsidian vault.

failed to get completions with error: ...re/nvim/lazy/blink.compat/lua/blink/compat/lib/utils.lua:9: bad argument #1 to 'pairs' (table expected, got boolean)

This leads me to the shallow_copy function, and it has to accept a table than a boolean. Within blink.compat, the only place this function is called is transformed_callback, which is used in source:get_completions. This function calls the source:complete function.

In our case, the source here is really the cmp_obsidian as defined in obsidian.nvim. I'm suspecting that this line is not returning the correct type for blink.compat to handle. (I could be wrong here, again I'm not very proficient in navigating in lua codes).

While this may also be fixed on the obsidian.nvim side, but it seems that it has not been updated for 7 months - I'm a bit concerned actually.

For others who seek a fix, you can specify Feb 6 commit of the blink.compat with

{ 'saghen/blink.compat', lazy = true, commit = 'c6093c0cbed51a57ba4b51866e1f031f24fa9d8b' },

stefanboca · 2025-02-11T05:08:31Z

Thanks for the detailed bug report! The fix was quite simple, and should be in blink.compat main as of Saghen/blink.compat@4104671.

patricorgi · 2025-02-11T05:28:10Z

Thanks for the detailed bug report! The fix was quite simple, and should be in blink.compat main as of Saghen/blink.compat@4104671.

Thank you so much!

DaitiDay · 2025-02-20T08:46:56Z

Sorry but I got lost among all the possible solutions presented, has a final solution been found?

pablodre · 2025-02-20T10:58:45Z

Sorry but I got lost among all the possible solutions presented, has a final solution been found?

The solution is to have someone review and merge this PR
feat(completion): blink.cmp support by adamtajti · Pull Request #817 · epwalsh/obsidian.nvim

DaitiDay · 2025-02-20T13:56:12Z

So it's just a matter of time, thank you 😄

kalyanoliveira · 2025-03-04T20:30:55Z

It would seem that this fork supports blink - correct me if I am wrong. Considering that the latest release (3.9.0) was on July 11, 2024, would it be safe to assume that it will not be merged in the near-future and, thus, the best workaround for now would be to use that fork instead of the official plugin?

Edit: just tried the fork today with opts = { completion = { blink = true } }, and it works perfectly!

ffricken · 2025-03-06T16:16:04Z

In fact, the fork was made by a couple of people from the community with the goal to maintain the plugin in the future! A couple of other issues are also already closed!

marko1777 · 2025-03-11T08:15:24Z

It would seem that this fork supports blink - correct me if I am wrong. Considering that the latest release (3.9.0) was on July 11, 2024, would it be safe to assume that it will not be merged in the near-future and, thus, the best workaround for now would be to use that fork instead of the official plugin?

Edit: just tried the fork today with opts = { completion = { blink = true } }, and it works perfectly!

@kalyanoliveira
Did you add anything to sources in blink?
I tried setting the completion to blink = true in the fork but still, I can't make the wiki link trigger work.

kalyanoliveira · 2025-03-11T16:30:56Z

This is how I setup blink with lazy.nvim:

        {
		"saghen/blink.cmp",
		dependencies = {
			"rafamadriz/friendly-snippets"
		},
		config = true
	}

This is how I setup obsidian:

		opts = {

			workspaces = {

				{
					name = "ob-vault",
					path = "~/monastery/ob-vault"
				},

			},

			completion = {
				blink = true
			},

		},

marko1777 · 2025-03-12T08:35:03Z

For me, I didn't get wiki completion for [[]] because I had nvim_cmp = false in completion, after removing it, I get completion, but it seems like it's not blink which prompts me, but cmp since I cannot go on the references with my key bindings and I get two suggestions boxes..

marko1777 · 2025-03-12T08:50:20Z

I found that you need to add obsidian to sources in blink to make it work, but it is still not perfect since the wiki link only get's into the reference list after you restart the LSP, and the completion is pretty slow..

sources = {
            default = { "obsidian", "obsidian_new", "obsidian_tags", "lsp", "path", "snippets", "buffer", "markdown" },
}

ffricken · 2025-03-12T20:59:30Z

@marko1777 would you be able to create an issue in the fork?

magnusriga · 2025-04-24T18:21:19Z

It says that it was merged, see obsidian-nvim#5, so it should work out of the box.

brianrodri · 2025-04-24T18:34:10Z

Is there anything left blocking this issue, then? It's not clear from this huge thread, and I keep seeing that things should be "working out of the box", which means we can close this, right?

TZProgrammer · 2025-04-24T18:35:44Z

Since this feature has been merged in the fork, I will be closing the issue.

kalyanoliveira · 2025-04-24T18:39:39Z

There are still some bugs with the fork, particularly during completion with aliases.

Would it be safe to assume that, given the closure of this issue, obsidian.nvim will never officially support blink.cmp, and that all questions, inquiries, and complaints should be directed to the fork?

ffricken · 2025-04-25T06:18:10Z

There are still some bugs with the fork, particularly during completion with aliases.

Would it be safe to assume that, given the closure of this issue, obsidian.nvim will never officially support blink.cmp, and that all questions, inquiries, and complaints should be directed to the fork?

Yes. This was one of the reasons the fork was created in the first place!

magnusriga · 2025-04-27T19:51:45Z

For me, I didn't get wiki completion for [[]] because I had nvim_cmp = false in completion, after removing it, I get completion, but it seems like it's not blink which prompts me, but cmp since I cannot go on the references with my key bindings and I get two suggestions boxes..

Same for me, I also needed nvim_cmp = true.

The completions you are seeing are likely from an LSP, e.g. marksman.

Note: The links created with marksman are not compatible with the Obsidian desktop application.

TZProgrammer added the feature request label Nov 15, 2024

bamdadfr added a commit to bamdadfr/config-nvim that referenced this issue Dec 16, 2024

plugins/obsidian: disable nvim-cmp for now

64e1904

epwalsh/obsidian.nvim#770

This was referenced Jan 27, 2025

feat(completion): blink.cmp support adamtajti/obsidian.nvim#1

Closed

feat(completion): blink.cmp support #817

Closed

benatouba mentioned this issue Feb 14, 2025

Blink support benatouba/obsidian.nvim#1

Merged

guspix mentioned this issue Feb 28, 2025

feat(completion): blink.cmp support obsidian-nvim/obsidian.nvim#5

Merged

TZProgrammer closed this as completed Apr 24, 2025

Support blink.nvim Autocomplete #770

Support blink.nvim Autocomplete #770

Comments

TZProgrammer commented Nov 15, 2024

🚀 The feature, motivation and pitch

Alternatives

Additional context

NickvanDyke commented Nov 27, 2024

codingluke commented Dec 4, 2024 • edited Loading

NickvanDyke commented Dec 4, 2024

sadtab commented Dec 7, 2024

Alan-TheGentleman commented Dec 13, 2024

sadtab commented Dec 13, 2024

paulwyszynski commented Dec 15, 2024

yuchenfei commented Dec 20, 2024

Muizzyranking commented Dec 21, 2024

sebszyller commented Dec 21, 2024

yuchenfei commented Dec 21, 2024

Muizzyranking commented Dec 22, 2024

stefanboca commented Dec 22, 2024 • edited Loading

shivayan-bora commented Dec 23, 2024 • edited Loading

paulwyszynski commented Dec 23, 2024

CaeChao commented Dec 23, 2024 • edited Loading

shivayan-bora commented Dec 24, 2024 • edited Loading

Muizzyranking commented Dec 24, 2024

brianrodri commented Dec 24, 2024 • edited Loading

CaeChao commented Dec 24, 2024 • edited Loading

Alan-TheGentleman commented Dec 24, 2024

Muizzyranking commented Dec 24, 2024

celfred commented Dec 27, 2024

Muizzyranking commented Dec 27, 2024

celfred commented Dec 27, 2024

rbmarliere commented Dec 27, 2024

celfred commented Dec 27, 2024

Muizzyranking commented Dec 27, 2024

ericsunplus commented Jan 17, 2025

ericsunplus commented Jan 17, 2025

Muizzyranking commented Jan 17, 2025

ericsunplus commented Jan 18, 2025

patricorgi commented Feb 11, 2025

stefanboca commented Feb 11, 2025

patricorgi commented Feb 11, 2025 • edited Loading

stefanboca commented Feb 11, 2025

patricorgi commented Feb 11, 2025

DaitiDay commented Feb 20, 2025

pablodre commented Feb 20, 2025 • edited Loading

DaitiDay commented Feb 20, 2025

kalyanoliveira commented Mar 4, 2025 • edited Loading

ffricken commented Mar 6, 2025

marko1777 commented Mar 11, 2025 • edited Loading

kalyanoliveira commented Mar 11, 2025

marko1777 commented Mar 12, 2025 • edited Loading

marko1777 commented Mar 12, 2025 • edited Loading

ffricken commented Mar 12, 2025

magnusriga commented Apr 24, 2025

brianrodri commented Apr 24, 2025

TZProgrammer commented Apr 24, 2025

kalyanoliveira commented Apr 24, 2025

ffricken commented Apr 25, 2025

magnusriga commented Apr 27, 2025

codingluke commented Dec 4, 2024 •

edited

Loading

stefanboca commented Dec 22, 2024 •

edited

Loading

shivayan-bora commented Dec 23, 2024 •

edited

Loading

CaeChao commented Dec 23, 2024 •

edited

Loading

shivayan-bora commented Dec 24, 2024 •

edited

Loading

brianrodri commented Dec 24, 2024 •

edited

Loading

CaeChao commented Dec 24, 2024 •

edited

Loading

patricorgi commented Feb 11, 2025 •

edited

Loading

pablodre commented Feb 20, 2025 •

edited

Loading

kalyanoliveira commented Mar 4, 2025 •

edited

Loading

marko1777 commented Mar 11, 2025 •

edited

Loading

marko1777 commented Mar 12, 2025 •

edited

Loading

marko1777 commented Mar 12, 2025 •

edited

Loading