Idea: Toggleable "MRU list" on top of all searches (most recently used)
Posted: Wed Apr 17, 2024 1:47 pm
Hi there!
(Older grouchy guy here, and a longtime (10+ years, not sure when, since forever) user of everything, but have never actually participated in the forum, just lurked a few times. I want to say huge thanks for this indispensable tool that has been on top of the list of things to install on any new machine I use for... yeah that long)
I'll skip an in depth usecase discussion and just come right to the suggestion - but suffice it to say I am after the times when you use everything to jump to often used files. And similarly more often used files...
TLDR: MRU list/section on top. "Jumplist" one might perhaps call it, not sure.
Short: I would love to be able to get a few lines (0..n, configurable) on top of any search result (regardless of sort for the search) displaying any Most Recently Used (MRU) items - i e that match some threshold criteria based on the runcount data (ideally also configureable, with some sensible defaults, atleast after some use it would become sensible
Little more details: Again - so, if given that I have toggled a proposed on, then: As I search; any items which have runcount data and which match a , would appear on top (likely sorted descending according to a ). The number of MRU lines / matches would be capped to the aforementioned , which I am guessing would be rather low by default. After the MRU lines/section, the rest of the search would appear as usual, sorted according to how the sort is set up in the UI using as normal (clicked column header, etc). (A common scenario would be for example that the MRU list would be populated at some point, but then as the search expression is added to as it is being written, there are no longer any candidates that match the MRU criteria expression.)
------
I have searched alot on the forum to see what other ideas, runcount based possibilities, and discussions that there have been regarding MRU - but I have not found this idea, so I figured I would add it. Jumping is one of many, many use cases for everything - and the use cases differ alot. But I think it is a common use case for many users.
If I have missed that this use case is already supported, I would love to learn how. I have read of using runcount in various ways which I interpret as addressing this need, but not in this way. Also, sorry if this idea is already there and I missed it.
Happy to try and clarify anything that is unclear about this idea, of course.
BR! /marcus
(Older grouchy guy here, and a longtime (10+ years, not sure when, since forever) user of everything, but have never actually participated in the forum, just lurked a few times. I want to say huge thanks for this indispensable tool that has been on top of the list of things to install on any new machine I use for... yeah that long)
I'll skip an in depth usecase discussion and just come right to the suggestion - but suffice it to say I am after the times when you use everything to jump to often used files. And similarly more often used files...
TLDR: MRU list/section on top. "Jumplist" one might perhaps call it, not sure.
Short: I would love to be able to get a few lines (0..n, configurable) on top of any search result (regardless of sort for the search) displaying any Most Recently Used (MRU) items - i e that match some threshold criteria based on the runcount data (ideally also configureable, with some sensible defaults, atleast after some use it would become sensible
Little more details: Again - so, if given that I have toggled a proposed
MRU/recently used flag
MRU criteria expression
MRU sort expression
MRU list maxcount
------
I have searched alot on the forum to see what other ideas, runcount based possibilities, and discussions that there have been regarding MRU - but I have not found this idea, so I figured I would add it. Jumping is one of many, many use cases for everything - and the use cases differ alot. But I think it is a common use case for many users.
If I have missed that this use case is already supported, I would love to learn how. I have read of using runcount in various ways which I interpret as addressing this need, but not in this way. Also, sorry if this idea is already there and I missed it.
Happy to try and clarify anything that is unclear about this idea, of course.
BR! /marcus