Replies: 2 comments 1 reply
-
I used the following minimal local lazypath = vim.fn.stdpath("data") .. "/lazy/lazy.nvim"
if not vim.loop.fs_stat(lazypath) then
vim.fn.system({
"git",
"clone",
"--filter=blob:none",
"https://github.com/folke/lazy.nvim.git",
"--branch=stable", -- latest stable release
lazypath,
})
end
vim.opt.rtp:prepend(lazypath)
require("lazy").setup({
{ "folke/tokyonight.nvim" },
{
"rest-nvim/rest.nvim",
commit = "1ce984c",
},
})
vim.cmd.colorscheme("tokyonight") And in the first installation Screencast following Screencast.2024-03-23.19.53.37.webm |
Beta Was this translation helpful? Give feedback.
-
Oh just found what the issue was.. For some reason my After cleaning it up and starting nvim now it installed the desired version.. Anyway it is working properly now.. I've done multiple tests by uninstalling ("x") and installing again.. it's now coming in the desired version.. nice! Thanks for the response and trying it out |
Beta Was this translation helpful? Give feedback.
-
Hi, trying to understand better these 3 properties..
Given the new version of Rest.nvim is broken ATM I'm trying to lock it to the previous stable version, and after trying out these 3 properties I noticed they aren't working as I thought they would..
I tried setting up all these 3 properties but Lazy always installs the latest version of the plugin..
I noticed that, if the specified plugin is already in the desired version in these properties, then okay Lazy stops looking for updates.. but if I'm doing a fresh new installation Lazy is going to the latest version even if I use "pin" property.. is this expected?
ie:
Thanks in advance
Beta Was this translation helpful? Give feedback.
All reactions