mini.pick buffers - absolute and relative filepath

[harg]

Contributing guidelines

• I have read CODE_OF_CONDUCT.md

Module(s)

mini.pick

Question

I use a lot the buffer picker and I noticed some inconsistencies :
when I open files with mini.files or mini.pick (files), it shows the relative path but when I open another one with "LSP Go To definition" (eg. mini.pick through mini.extra), it is opened with the absolute filepath.

Is there a way to overwrite the picker to display only the relative path to the current working directory (cwd) and improve the readability?
Thanks!

[echasnovski]

Adjusting that in 'mini.extra' itself should straightforward, but I am afraid I can not reproduce. I tried both LuaLS and gopls, and both result in relative paths shown in both :Pick buffers and :buffers.

Would you mind, please, provide an exact steps to reproduce this? Including LSP server (I assume, gopls?), repo (some already existing public repo or dummy one created by you specifically for this), and exact file-position pair at which :Pick lsp scope='definition' is executed.

[harg]

Repo : https://github.com/harg/gomini
LSP server : gopls v0.17.1
OS: Windows 10
Nvim : tested with latest stable or the pre-release

:Pick lsp scope='definition' on main.go l: 6, c:14

:Pick buffers :

If I run again :cd c:\CODE\gomini, it displays the relative path :

Thank you for your support !

[echasnovski]

Thanks for the repro steps!

If I run again :cd c:\CODE\gomini, it displays the relative path :

I indeed can reproduce and this was the main clue to this: I have auto root set up which seems to act as that manual :cd step.

The thing is, 'mini.pick' already should open any file with relative path, but it doesn't do that here for some reason. I'll take a look.

[harg]

Indeed, last night i ended up with this :

-- UGLY WORKAUROUND : reapply the working directory on file/buffer enter in order to set relative filepath in buffer list
vim.api.nvim_create_autocmd({ "BufEnter", "BufWinEnter" }, {
  pattern = "*",
  callback = function()
    local initial_cwd = vim.fn.getcwd()
    vim.cmd("silent cd " .. initial_cwd)
  end,
})

[echasnovski]

This should now be resolved on latest main. It required hacky workaround thanks to the observation from here that any directory change seems to "reset" :buffers output (i.e. short buffer names).