Made the same mod in my config, thanks for adding here!

Thank you @folke for accepting the PR. On the Telescope subject, in my config I also have nvim-telescope/telescope-file-browser.nvim setup in the following way

{
    "nvim-telescope/telescope-file-browser.nvim",
    dependencies = { "nvim-telescope/telescope.nvim" },
    config = function()
        require("telescope").load_extension "file_browser"
    end,
    keys = {
        { "<leader>fd", "<cmd>Telescope file_browser<cr>", desc = "File Browser (cwd)" },
    },
}

Would you be interested in having this merged too ?

I don't think it's all that useful, given that we already have neo-tree and Telescope find_files.

I agree. I just thought it would be worth it asking.

Finally, I also have jpalardy/vim-slime setup to work with the Julia and Python REPLs with tmux. I think this is even less worth it merging, but I think others would like having this template to build their configs upon (there aren't that many examples on how to nicely work with REPLs and NeoVim).

Where do you think would be the ideal place to showcase it?

-- slime (REPL integration)
{
    "jpalardy/vim-slime",
    keys = {
        { "<leader>rc", "<cmd>SlimeConfig<cr>",               desc = "Slime Config" },
        { "<leader>rr", "<Plug>SlimeSendCell<BAR>/^# %%<CR>", desc = "Slime Send Cell" },
    },
    config = function()
        vim.g.slime_target = "tmux"
        vim.g.slime_cell_delimiter = "# %%"
        vim.g.slime_bracketed_paste = 1
    end,
},

You can use https://github.com/LazyVim/LazyVim/discussions/categories/show-and-tell for that.

Hi! I just wanted to let you know that I changed the Telescope keybindings to make them more consistent with cmp / signature help and hover.

<c-f> and <c-b> should now be used for scrolling the preview. This is the same as used for the cmp doc window, signature help and for scrolling the hover window.

I've also removed the new <c-i> and <c-j> mappings since in other places we also use the default way of navigating a list with <c-n> and <c-p>. Again this is to make all mappings more consistent.

You can of course still override this in your own mappings if that's what you prefer.