-
Notifications
You must be signed in to change notification settings - Fork 177
New issue
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
feature: Remembering Current Entry State After Toggling Trouble Window #367
Comments
Upvote! |
Upvote |
Upvote! |
Upvote |
Upvote! |
When i saw that trouble v3 is released, i was hoping to much this feature would be included. But apparently it doesn't. When toggeling the quickfix with |
Added and enabled by default. |
Not working for me. consider this minimal config: -- DO NOT change the paths and don't remove the colorscheme
local root = vim.fn.fnamemodify("./.repro", ":p")
-- set stdpaths to use .repro
for _, name in ipairs({ "config", "data", "state", "cache" }) do
vim.env[("XDG_%s_HOME"):format(name:upper())] = root .. "/" .. name
end
-- bootstrap lazy
local lazypath = root .. "/plugins/lazy.nvim"
if not vim.loop.fs_stat(lazypath) then
vim.fn.system({ "git", "clone", "--filter=blob:none", "https://github.com/folke/lazy.nvim.git", lazypath, })
end
vim.opt.runtimepath:prepend(lazypath)
-- install plugins
local plugins = {
"folke/tokyonight.nvim",
{
"folke/trouble.nvim",
branch = "dev",
lazy = false,
opts = {
follow = false,
restore = true,
auto_preview = false,
auto_refresh = false,
},
},
-- add any other plugins here
}
require("lazy").setup(plugins, {
root = root .. "/plugins",
})
vim.cmd.colorscheme("tokyonight")
-- add anything else here Then I open nvim with:
|
Should be fixed now. The problem was that qf items did not have a unique |
unfortunately still not working with the same example |
UPVOTE!!!! |
Allright, I now used your repro and at least that should be fixed now. Would be great if you can confirm! |
it works when toggeling the trouble window off and on once. if I toggle it off and on twice, the entry is lost. additionally it also does not remember the entry when the trouble window resides in a edgy window and the whole edgy bar is closed with Last but not least, jumping to the next entry of the last toruble window when the trouble is closed with |
…ouble window was never visisted. See #367
I changed the way we track/restore positions, so that shoudl fix that toggle twice. For me it all works with edgy, so maybe that also fixes that. About that last thing, I dont fully understand what you mean? |
yes that works now thank you
you are right, edgy is not the problem. The problem is that i advance the entries with: |
in vanilla (n)vim, you can populate a quickfix list and jump to the next entry with in trouble you can populate the trouble list (lets say the |
Quite similar to the thing I mentioned above. Maybe this could be better explained in a dedicated issue.. |
Did you check the docs?
Is your feature request related to a problem? Please describe.
Hello,
I have completely replaced my Quickfix list with Trouble, and I love its features. However, there is one thing that bothers me. Trouble doesn't seem to remember its current entry when I toggle it off and on again. In contrast, the native Quickfix window remembers its current entry when toggling with
cclose
andcopen
.Describe the solution you'd like
Trouble remembers it's current entry
Describe alternatives you've considered
Additional context
No response
The text was updated successfully, but these errors were encountered: