Skip to content
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

Select/set current quickfix list by id/number / goto non-current list entry #3699

Closed
blueyed opened this issue Dec 16, 2018 · 6 comments
Closed

Comments

@blueyed
Copy link

blueyed commented Dec 16, 2018

  1. Currently there appears to be only :colder/:cnewer to select a quickfix list, which uses relative counts (by number), and therefore it is not trivial to select a specific number (that you can get using getqflist({'id': qfid, 'nr': 1}), but you would have to get the current number and then do a relative :colder/:cnewer. I think it would be nice being able to select a specific list by id. Not sure if selection by number is useful, because this might rotate (there are only 10).

  2. My use case / idea is to temporarily switch the lists for :cc/:ll (wrapped by a command to go to nearest entries according to the cursor position).
    For this specific use case it would be best if temporarily switching the current list would not be necessary in the first place, i.e. it would be good if :cc / :ll could be called on a non-current list - likely done best through a new function?! - but maybe also :[id]cc [count] could be used?!
    This way plugins could go to next/prev/specific entries from their list, which must not be the one currently being displayed in the quickfix window.

@vim-ml
Copy link

vim-ml commented Dec 16, 2018 via email

@vim-ml
Copy link

vim-ml commented Dec 17, 2018 via email

@blueyed
Copy link
Author

blueyed commented Dec 21, 2018

I've reviewed #3701, but not really tried it - looks good!

As for 1.:

Can we extend the :chistory command to take a list number
in the stack?

That sounds like a good solution.

@vim-ml
Copy link

vim-ml commented Jan 13, 2019 via email

@blueyed
Copy link
Author

blueyed commented Jan 14, 2019

Thank you.
I have not tried it yet still, but assume this to be fixed.

@blueyed blueyed closed this as completed Jan 14, 2019
@vim-ml
Copy link

vim-ml commented May 6, 2019 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants