Same problem here, but in Lazyvim

I'm not able to reproduce this. Right after opening a file, can you print out the values?

:echom 'g:minimap_width: ' .. g:minimap_width
:echom 'g:minimap_auto_start: ' .. g:minimap_auto_start
:echom 'g:minimap_auto_start_win_enter: ' .. g:minimap_auto_start_win_enter
:mes

I'm not familiar with that method of setting up plugins and config, so I'm wondering if the value is not being set properly during startup.

All three give me unknown variable errors.

If I instead put it at the top-level of my vimrc, I get:

g:minimap_width: 10
g:minimap_auto_start: v:true
g:minimap_auto_start_win_enter: v:true

Is it possible that this plugin just does not load correctly when set up via lazyvim?

Ah, that's probably it. Right now it's checking for the value of 1 explicitly:

if g:minimap_auto_start == 1

We'll need to update this to do a proper boolean check.

As a workaround, try setting the value to 1 rather than true, does that work?

I tried setting it to 1, unfortunately no change.

Okay, it seems to work for me now:

vim.g.minimap_width = 10
vim.g.minimap_auto_start = true
vim.g.minimap_auto_start_win_enter = true
table.insert(lvim.plugins, {
    'wfxr/minimap.vim',
    build = "cargo install --locked code-minimap",
})

The problem was a combination of:

1. config() sets these variables too late
2. I had the cmds line uncommented at some point, which made lazy nvim only load this plugin when actually running one of those commands

The true/1 distinction is irrelevant, it seems.

Edit: This also works:

table.insert(lvim.plugins, {
    'wfxr/minimap.vim',
    build = "cargo install --locked code-minimap",
    init = function()
        vim.g.minimap_width = 10
        vim.g.minimap_auto_start = 1
        vim.g.minimap_auto_start_win_enter = 1
    end
})

I am suffering the same issue not solved using anything mentioned.

When using the workaround @haasn noted I get the minimap showing (great) but without the background highlight (darn).

If the 'cmd = ' line is missing then the highlight background doesn't show.

I use lazy.nvim, this is my config:

return {
    "wfxr/minimap.vim",
    build = "cargo install --locked code-minimap",
    lazy = false,
    cmd = { "Minimap", "MinimapClose", "MinimapToggle", "MinimapRefresh", "MinimapUpdateHighlight" },
    init = function()
        vim.cmd("let g:minimap_width = 10")
        vim.cmd("let g:minimap_auto_start = 1")
        vim.cmd("let g:minimap_auto_start_win_enter = 1")
    end,
    -- config = function()
    --     vim.cmd("let g:minimap_width = 10")
    --     vim.cmd("let g:minimap_auto_start = 1")
    --     vim.cmd("let g:minimap_auto_start_win_enter = 1")
    -- end,
}

the lazy = false is very important.then write your config to init.

Finish this,it will look like normal.

set lazy = false,the plugins will load when you open nvim.

If it still doesn't work, you should check if the build is successful. try code-minimap --version:

For me, in lazyvim, this does open minimap on startup, but, doesn't show the background highlight (or cursor position) in the minimap - and I disabled all other plugins and custom settings:

  {
    'wfxr/minimap.vim',
    build = "cargo install --locked code-minimap",
    cmd = {"Minimap", "MinimapClose", "MinimapToggle", "MinimapRefresh", "MinimapUpdateHighlight"},
    lazy = false,
    init = function()
      vim.cmd("let g:minimap_width = 10")
      vim.cmd("let g:minimap_auto_start = 1")
      vim.cmd("let g:minimap_auto_start_win_enter = 1")
    end,
  },

I also get:

❯ code-minimap --version
code-minimap 0.6.4

I have also encountered this issue, but after deleting it. Use 'cargo install code-minimap' on the terminal to install code-minimap and ensure no errors are reported. Then locate minimap.vim in nvim-data and delete the minimap.vim folder. Re enter nvim, it will be downloaded again, and then it is ready.

You can give it a try. @mclarkson

I am also use lazyvim,and no have any problem.

For me, simply put "init" instead of "config" does the job. I'm using LunarVim. Hope it helps someone out there! ;-)

  {
    'wfxr/minimap.vim',
    build = "cargo install --locked code-minimap",
    --cmd = { "Minimap", "MinimapClose", "MinimapToggle", "MinimapRefresh", "MinimapUpdateHighlight" },
    init = function()
      vim.g.minimap_width = 10
      vim.g.minimap_auto_start = true
      vim.g.minimap_auto_start_win_enter = true
      vim.g.minimap_highlight_range = true
      vim.g.minimap_highlight_search = true
    end,
  },

After a bit of research, I found that in LunarVim the background highlight disappears after any activity: for example, if you set the option lazy = true and open the minimap with :MinimapToggle, then the highlighting will show up as it should. But after doing :w it disappears.

If you set lazy = false, then some internal activity will occur during startup, and background highlighting will not be displayed.

Okay, it seems to work for me now:

vim.g.minimap_width = 10
vim.g.minimap_auto_start = true
vim.g.minimap_auto_start_win_enter = true
table.insert(lvim.plugins, {
    'wfxr/minimap.vim',
    build = "cargo install --locked code-minimap",
})

The problem was a combination of:

1. config() sets these variables too late
2. I had the cmds line uncommented at some point, which made lazy nvim only load this plugin when actually running one of those commands

The true/1 distinction is irrelevant, it seems.

Edit: This also works:

table.insert(lvim.plugins, {
    'wfxr/minimap.vim',
    build = "cargo install --locked code-minimap",
    init = function()
        vim.g.minimap_width = 10
        vim.g.minimap_auto_start = 1
        vim.g.minimap_auto_start_win_enter = 1
    end
})

I have some issue, and I also use lunarVim. This code can fix my problem, I rewrite it from config to init.

Seems to have a lot more to do with LunarVim than this plugin. I'll leave this open in case there is more discussion, but I'm not seeing anything that needs to change in minimap.vim.

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.