Minimal init.lua for bug report reproduction steps

[mrjones2014]

For reporting bugs, you can base your minimal init.lua on the following:

local root = vim.fn.fnamemodify('./.repro', ':p')

-- set stdpaths to use .repro
for _, name in ipairs({ 'config', 'data', 'state', 'cache' }) do
  vim.env[('XDG_%s_HOME'):format(name:upper())] = root .. '/' .. name
end

-- bootstrap lazy
local lazypath = root .. '/plugins/lazy.nvim'
if not vim.loop.fs_stat(lazypath) then
  vim.fn.system({
    'git',
    'clone',
    '--filter=blob:none',
    '--single-branch',
    'https://github.com/folke/lazy.nvim.git',
    lazypath,
  })
end
vim.opt.runtimepath:prepend(lazypath)

-- install plugins
local plugins = {
  -- do not remove the colorscheme! it makes testing nicer
  'folke/tokyonight.nvim',
  {
    'mrjones2014/legendary.nvim',
    dependencies = {
      -- place your `vim.ui.select()` handler plugin here
      -- for example:
      -- 'nvim-telescope/telescope.nvim',
      -- 'stevearc/dressing.nvim',
    },
  },
  -- add any other pugins here
}

require('lazy').setup(plugins, {
  root = root .. '/plugins',
})

require('dressing').setup()

require('legendary').setup({
  -- add any options here
})

-- add anything else here
vim.opt.termguicolors = true
-- do not remove the colorscheme! it makes testing nicer
vim.cmd([[colorscheme tokyonight]])

[tsyroid]

This is very cool, "non-jank" stuff MrJones. I've used some similar "minimal init" files before, but they were more generic. This not only specifically targets Legendary, it also clearly shows me HOW to customize it for Legendary -- which cycles back to your blog post about writing code without requiring comments, and my needs a few weeks back to understand better the bootstrap process.

Short story: Something like this needs to be bundled within every plugin's tree somewhere.

Aside: I clearly need to find a better way to track/follow what's going on in repos I'm interested in. I only discovered this today, 8 days after it was posted.

[mrjones2014]

This isn’t in the repo tree because it’s only really needed when trying to reproduce issues that are hard to reproduce. Didn’t seem necessary to have in the actual repo, thus I put it here in discussions. I link to this from the new issue template (you’ll see if you click “New Issue” then select “Bug Report”).

And credit where credit is due, I pretty much took this from Telescope.nvim’s issue template and customized it to be for legendary instead of telescope.

[tsyroid]

All good. Just noting or commenting more on the wonder of Github. So much here. So much to be discovered. But we’re all still trying to find our way on how to do that in a way that reflects our personal levels of want/need. Struggle with this issue every day. It just becomes important to call-out when I see something that fills a gap, that I didn’t know I had, on a thread a missing, that was buried somewhere in this byzantine called GitHub. Best, /tom

…

On Mar 27, 2022 at 08:02:04, Mat Jones ***@***.***> wrote: This isn’t in the repo tree because it’s only really needed when trying to reproduce issues that are hard to reproduce. Didn’t seem necessary to have in the actual repo, thus I put it here in discussions. I link to this from the new issue template (you’ll see if you click “New Issue” then select “Bug Report”). And credit where credit is due, I pretty much took this from Telescope.nvim’s issue template and customized it to be for legendary instead of telescope. — Reply to this email directly, view it on GitHub <#93 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAGTYGUZSTVPLXZSYEIOB6LVCBZ6ZANCNFSM5REI7DNA> . You are receiving this because you commented.Message ID: ***@***.*** com>

[danielo515]

Can I copy this to any random file on my disk and start nvim with nvim -u path/to/this/init.lua and get it working without affecting my main nvim install?

[mrjones2014]

I figured it out, it’s a in the minimal init. I’ve edited it. Should work now.

[danielo515]

May I see a diff of the changes? I would love to patch it in my local copy without having to start from scratch.
Thanks!

[danielo515]

Ok, maybe is the addition of vim.g.loaded_remote_plugins = "" ?
How is that affecting in such a drastic way?

[mrjones2014]

It has something to do with the way that Neovim loads remote plugins, I think. Not sure exactly.

[mrjones2014]

Yes that is the line I changed.

[towry]

How to use this minimal file?

[towry]

1. save to /tmp/init.lua
2. nvim -u /tmp/init.lua