bug: `lazy.core.util.norm` resolves `~` path differently from Neovim about lazy.nvim HOT 5 CLOSED

I would write a PR for this, however I can't really test it quickly, right now.

There's only 3 locations os_homedir is called:

lua/lazy/manage/process.lua:96:    opts.cwd = uv.os_homedir()
lua/lazy/core/util.lua:57:    local home = vim.uv.os_homedir()
lua/lazy/core/cache.lua:54:    local home = uv.os_homedir() or "~"

I think the process.lua one doesn't matter much since it's a fallback for internal command execution, I'm not sure about the cache.lua one though.

from lazy.nvim.

This seems to be more a bug with uv.os_homedir()? Please report a bug there instead.

from lazy.nvim.

I don't think it is? Using $HOME on Windows is not standard and a quirk of Vim. libuv returning %USERPROFILE% is objectively correct (for libuv) but Vim does it that way.

from lazy.nvim.

If libuv is returning the correct directpry, then I dont see what the issue is.

Anyway, just use a full path to point to the directory you need

from lazy.nvim.

The issue is that (Neo)vim does something that people rely on, and Lazy (a neovim plugin) doesn't follow that convention.

libuv shouldn't follow what vim does, but vim plugins should probably follow vim.

Either way, I just used expand('~') myself.

from lazy.nvim.