Closed MrRothstein closed 1 year ago
Hm, the new LazyExtras
use this file. I was under the impression that this was the only way to sync your extras with the new LazyExtras.
I see. The problem I'm seeing is the file as it's created initially contains a full path to files under the LazyVim install:
{"hashes":{"\/home\/<REDACTED>\/.local\/share\/nvim\/lazy\/LazyVim\/NEWS.md":"2035"},"extras":[]}
This path is different between my WSL and Mac installs. Ignoring the files is probably not a good fix for it though. At first I thought it was just using this file to track if it already showed the news...
@folke it seems a bit bad to store the full path like that to the NEWS.md
. Could for example reveal corporate usernames if stored in your dotfiles... Maybe you could avoid storing the full path and instead use ~
or $HOME
in the path, or some completely different approach?
Fixed in the meantime.
Now it will look be pretty-printed, sorted and without full paths. Will make a new release later.
{
"extras": [
"dap.core",
"test.core",
"coding.codeium",
"coding.copilot",
"coding.yanky",
"dap.nlua",
"lang.json",
"lang.omnisharp",
"lang.tailwind",
"lang.typescript",
"lang.yaml",
"linting.eslint",
"ui.edgy",
"ui.mini-animate",
"util.dot",
"util.mini-hipatterns",
"vscode",
"editor.aerial"
],
"news": {
"NEWS.md": "2035",
"doc/news.txt": "13972"
}
}
Entries in this file are host specific and should not be shared across installs