4513ECHO / vim-readme-viewer

📖 Viewing plugin's README easily like vim help
MIT License
28 stars 4 forks source link

Repository path is missing with packer.nvim #2

Open jemag opened 2 years ago

jemag commented 2 years ago

I have tried several Readme.md and most seem to work, however, for some reason, when i try to view the readme of telescope.nvim (https://github.com/nvim-telescope/telescope.nvim) I get the following: image

image

4513ECHO commented 2 years ago

Maybe I fixed. Please retry.

jemag commented 2 years ago

@4513ECHO Well it does not show error but it says that the readme file does not exist even though it is there: Error: image

Plugin directory: image

It works for plugin telescope-dap.nvim: image

but plugin directory is similar: image

jemag commented 2 years ago

I think I know why, I checked packer_compiled.lua, and for some plugins (like telescope) it does not show the path or URL, but rather only_config: packer_compiled.lua

  ["telescope.nvim"] = {
    after = { "session-lens", "telescope-harpoon.nvim", "telescope-ui-select.nvim", "telescope-vim-bookmarks.nvim" },
    loaded = true,
    only_config = true
  },

I am not sure what is causing this, since the plugin specification is similar for telescope.nvim

    use({
      "nvim-telescope/telescope.nvim",
      config = function()
        require("plugin-configs.telescope-config")
      end,
    })

and for telescope-dap.nvim

    use({
      "nvim-telescope/telescope-dap.nvim",
      config = function()
        require("telescope").load_extension("dap")
      end,
    })

but telescope-dap.nvim has proper path and url: packer_compiled.lua

  ["telescope-dap.nvim"] = {
    config = { "\27LJ\2\nH\0\0\3\0\4\0\a6\0\0\0'\2\1\0B\0\2\0029\0\2\0'\2\3\0B\0\2\1K\0\1\0\bdap\19load_extension\14telescope\frequire\0" },
    loaded = true,
    path = "/home/jemag/.local/share/nvim/site/pack/packer/start/telescope-dap.nvim",
    url = "https://github.com/nvim-telescope/telescope-dap.nvim"
  },
4513ECHO commented 2 years ago

Hmm, this is difficult problem. I keep opening this untill that packer's issue is fixed.

axieax commented 2 years ago

Hello, I've encountered this similar issue in my plugin as well. I managed to fix it here. I think this could be helpful for you, and should be quite an easy fix since you only need the plugin path. Hope it helps!

4513ECHO commented 2 years ago

@axieax Thanks! It is very helpful for me, I'll try to include the codes to the plugin.

Shougo commented 2 years ago

This issue can be closed?