It would be handy if thunar allowed for restricting the displayed files to those matching either a globbing pattern or a regular expression. For example, I have a folder with hundreds of (generated) files like foo.x foo.y foo.z foo.pdf foo2.x foo2.y foo2.z foo2.pdf ... Right now, I'm only interested in the PDF files. So I'd like to restrict the view to the glob pattern "*.pdf" or the regular expression "\.pdf$". This feature request is probably very related to #7514.
Already available.
Could you please elaborate? Is it available in the current git master, or is it a hidden feature with no menu entry? Or am I only too blind to find it?
What he means is that you can use Ctrl+S to select files that match a certain pattern. But you cannot filter the displayed files. That's something we could implement in the future, probably in combination with a global search feature (e.g. based on Tracker).
Ok, I understand. Well, my use-case is that I generate tons of files into some directory (graphs, xml, and visualization PDFs). Now I want to check some PDFs, but of course I don't want to select all 300 of them and fire up 300 evince instances. With respect to a global search: I'm not completely sure how that relates to my wishlist item. Basically, what I was thinking of is more or less an enhanced variant of "Show hidden files", aka "Show only files matching the given pattern". Clearly, "[X] Show hidden files" corresponds to ".*" with the more general facility, and "[ ] Show hidden files" corresponds to "^[^.].*".
(In reply to comment #4) > With respect to a global search: I'm not completely sure how that relates to my > wishlist item. Well, UI-wise it kinda does.
I second this feature request. I too have directories with a lot of files, and the quickest way to find the one I search, when I don't remember exactly its name, is to restrict the view to the files matching a given pattern : sometimes I have to open a rox-filer window, just to perform that filtering, it would be great if thunar implemented it.
*** This bug has been marked as a duplicate of bug 2316 ***