We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Hi,
I'm using harpoon2. When I start neovim and directly jump to the following buffers using:
vim.keymap.set("n", "<leader>1", function() harpoon:list():select(1) end) vim.keymap.set("n", "<leader>2", function() harpoon:list():select(2) end)
vim.keymap.set("n", "<leader>1", function() harpoon:list():select(1) end)
vim.keymap.set("n", "<leader>2", function() harpoon:list():select(2) end)
my statusline always shows an absolute path for the second one instead of a relative one.
If I start neovim and cycle through my buffers using
vim.keymap.set("n", "hn", function() harpoon:list():next() end)
all files are shown correctly with their relative paths. Now I can also use select and the relative paths are still shown correctly.
The text was updated successfully, but these errors were encountered:
Ok, I found out this doesn't happen when using lualine with relative paths enabled. Only when defining my own statusline with
local statusline = { ' %f', '%r', '%m', '%=', '%{&filetype}', ' %2p%%', ' %3l:%-2c ' } vim.o.statusline = table.concat(statusline, '')
Seems to be a problem with the %f
Sorry, something went wrong.
No branches or pull requests
Hi,
I'm using harpoon2. When I start neovim and directly jump to the following buffers using:
vim.keymap.set("n", "<leader>1", function() harpoon:list():select(1) end)
vim.keymap.set("n", "<leader>2", function() harpoon:list():select(2) end)
my statusline always shows an absolute path for the second one instead of a relative one.
If I start neovim and cycle through my buffers using
vim.keymap.set("n", "hn", function() harpoon:list():next() end)
all files are shown correctly with their relative paths. Now I can also use select and the relative paths are still shown correctly.
The text was updated successfully, but these errors were encountered: