Closed dwelle closed 6 years ago
Can't repro anymore.. will re-open if persists.
Got it.. it happens not when you just remove match, but if you remove all matches for given file. Then the cursor in search UI is reset to top.
If you remove all matches for given file, moving to top is OK. What do you expect in this scenario? I need more detailed example, number of files, each content of files, search word input, "refactoring" you do to reproduce issues... and so on..
I think I get what you wanted to report, but it's not fixable with technical reason. There is NO closest item when originally-cursor-placed-file are removed, narrow-editor is not tracking order of item(no previous/next file tracking). In ag/rg result, ouput are retrieves in separate chunks and asynchronously. So no order(which file comes after which file) are pre-determined. It might change on each search. That's why we cannot decide which is the closest file when all cursor-placed-file's-items are removed.
I see, thanks anyway :)
steps:
what should happen:
The search provider should put the cursor on the closest next (or previous) line to the one being removed.
Narrow
0.65.0
, Win7, Atom1.26.1