You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
when opening nvim from outside project folders, it would be useful if the paths shown in the Trouble window would be relative to the lsp root. for example, below i opened nvim from just outside of dotfiles/, a git repo
Describe the solution you'd like
i would like the path to remove dotfiles/ since it's a git repo and my lsp root is dotfiles/. i can see how others may prefer showing a relative path to the pwd, which is what Trouble current does. so maybe this can be an option?
Describe alternatives you've considered
a path_display option as a function for further customization like telescope.nvim has
path_display=function(_, path)
localtail=require("telescope.utils").path_tail(path)
returnstring.format("%s (%s)", tail, path)
end
Additional context
i work in a large codebase with many projects and subprojects. i often open nvim from any directory
The text was updated successfully, but these errors were encountered:
Did you check the docs?
Is your feature request related to a problem? Please describe.
when opening nvim from outside project folders, it would be useful if the paths shown in the Trouble window would be relative to the lsp root. for example, below i opened nvim from just outside of
dotfiles/
, a git repoDescribe the solution you'd like
i would like the path to remove
dotfiles/
since it's a git repo and my lsp root isdotfiles/
. i can see how others may prefer showing a relative path to the pwd, which is what Trouble current does. so maybe this can be an option?Describe alternatives you've considered
a
path_display
option as a function for further customization like telescope.nvim hasAdditional context
i work in a large codebase with many projects and subprojects. i often open nvim from any directory
The text was updated successfully, but these errors were encountered: