Yes, there's a command called "Empty Trash Items", which you can assign to any hotkey or access via the command palette. You can also right click on the trash in the left sidebar.
Hello! I can't promise anything on this topic yet, it's on my list, but it's fairly low priority right now.
The program was written in C with no dependencies, so introducing a huge dependency like that isn't an option. But I appreciate the advice!
I'm curious, how did you conclude that AccessKit is a huge dependency? The binary size does vary by platform, with the Linux backend being especially large due to its use of a pure-Rust implementation of D-Bus. But the Windows x64 DLL is 268 KB, and the macOS x86-64 dylib is 437 KB stripped. The impact of the static library on your binary size will probably be about the same, or maybe a little less because most applications don't require all of the little setter and (especially) getter functions. I'm not happy with the size on Linux, but I think it's acceptable on Windows and macOS, given that accessibility is, in many contexts, a must-have.
Sorry, I based this on your comment "If you can accept a Rust dependency". I haven't actually looked into it yet, but I'll check it out, thanks for sharing.
However, I'd still prefer to go with my own solution, if possible, for tighter integration.
Speed, modern UI, rearangable panels & tabs, globaly accesable and remmapable all actions via cmd palette, GoTo window, batch rename...
And many more things to come. Since this was built from scratch, a lot of time and enginering effort was put into building a solid base. I'm in a phase where adding new stuff is fairly frictionless, so it's gonna get a lot better in the coming months.
That being said, it's only 3 years old, very young compared to other long time players. So, it's not comparable feature for feature, yet.
Yes, the separation between folders and files is a toggleable option. You can sort by date modified. Also, you should try it yourself, it's in free beta. :)
Hey, thanks! Yes, I know about Fman. I’ve tried pretty much all file explorers on Windows, a fair number on Linux, and fewer on macOS. I watched that video a couple of years ago, it had some nice insights. Thanks for sharing that.
I've been talking about File Pilot since the early days of the project, so I managed to build a following on Twitter and Discord, along with a decent number of email subscribers. I'm hoping that'll be enough to spread the word.
I'm sorry Fman didn't work out for you as a business. But truth be told, you need to deliver something exceptional to compete with established players. While I don't see other file explorer alternatives as direct competition, I do think File Pilot will bring a breath of fresh air. We'll see how it goes!
That's not exceptional IMHO. It's a good effort, but not exceptional. Exceptional apps scream "wow" and are feature rich, with great UI/UX. Example of exceptional apps are Obsidian, TablePlus, Transmit (by panic), Sublime Text, VSCode. File Pilot has that "wow" factor and the features.
It does not integrate with Everything. It's already blazingly fast with the regular WinAPI for indexing. However, MFT indexing (which Everything uses) will be added as built-in support in the near future. It will be an opt-in option for users.
There are a couple of reasons why I didn't want to make MFT the default.
a) It requires admin access.
b) It's NTFS specific, which means you need to write different logic for other file systems anyway.
c) It's not officially documented or supported by Microsoft. It was reverse-engineered.
There is "blazingly fast" where you also have to only include SSDs, still see your root drive taking seconds to populate data for, and still requiring admin for the whole app with those ugly underlines otherwise..
And then there is literally instant, for literally everything, while the app itself is in normal mode and thus preserves the non-admin benefits.
a) Not for the app, only for Everything
b) Those other file systems could also be indexed by Everything (though via a slower mechanism). Also given the primacy of NTFS, I'd definitely trade the ability to have folder sizes for drives I rarely use for the instant calculations on drives I use all the time
c) Good. Waiting for MS docs could mean a few more decades of wasted potential
