I don't have a strong use case for this, but I do run into this "issue" while in my downloads folder, which is often full of random/temporary files, and I usually have some of them "hidden away" using collapsed groups to remove some of the clutter while I procrastinate ![]()
While working on my non-hidden files I sometimes want to rename the visible files (i.e. the non-collapsed groups), and I usually use inline renaming.
A scenario could look like this:
I here have renamed the .mkv file using inline rename, and I want to move down to also rename the accompanying .srt file.
Using up/down to move across the files would normally skip over the collapsed files, but when in inline rename mode, it will select the next file (regardless of it being "hidden" inside a collapsed group or not) and spring open the collapsed group:
A file that seemed so close, is now so far, far away
![]()
Yes, I could press enter to exit inline rename mode, then move down outside inline rename mode to avoid The Great Uncollapsing Event of 2026, and then hit F2 again without much effort -- but my muscle memory tells me that up/down will normally skip over collapsed files and take me to the .srt file as a shortcut -- and since I do want to keep renaming files, my monkey brain thinks exiting inline rename mode is counter productive, so I press down while still in inline rename mode.
So this is just a longwinded way of saying I think it would make more sense for the inline rename to respect collapsed groups just like normal "file lister surfing" does.
Maybe it could be a setting, but to be honest, I find it hard to see a scenario where the user actually expects the uncollapsing to play out in this way and actually wants to select a non-displayed file while in the inline rename mode, but maybe I'm wrong.
For your consideration™
![]()

