![]() I'll try to mirror your marketing as closely as possible. I feel like I should test the claim of how many people want an `Everything` equivalent on Linux: I'll make it, package it with a MVP GUI, and mention it on a few forums in addition to posting a show HN here.įor ideal reproducibility, let me know which forum(s) you initially got traction on. I have to also admit that I've looked at stuff in the past, gone "No one could possibly want that, at that price point" and been horribly wrong. Honestly, I'm still very skeptical that even a $100 target is possible. > You can easily make $100 in donations with this. I think that what you have produced satisfies what the target market wants. My point was that the incentive to produce something like `Everything` on Linux just isn't aligned with what the target market wants or needs. I hope that I didn't come off as dismissive of your hard work or of being disrespectful of what you have delivered. Gl: aliased to git log -all -pretty=oneline -pretty=format:"%Cgreen%h%Creset %s %Cred%d%Creset" -color=always | fzf -ansi -preview 'git show -pretty=medium -color=always $(echo | cut -d" " -f1)' | cut -d" " -f1įirstly, I appreciate you taking the time to engage with me. The possibilities are endless.Įdit: Here a short video showing my basic git log alias: Or a blazingly fast PDF-content searcher that opens the PDF in the end. let's you search and multiselect (enqueue) your music collection and on each entry display audio metadata using a custom script. It is powerful because it also can do things like running special commands ("preview") on the currently selected entry/line and allows for displaying the output in a separate pane. If you don't know it: it gives you a fuzzy search on things you pipe into it. I can't recommend fzf enough you can do some really powerful stuff with it. Or do you mean something else?įd if you want to find stuff in filenamesįzf for when you want a fuzzy menu type of search on top of this. You can also disable auto index updates when the application is launched, if you prefer manual or scheduled index update instead. The index is cached and loaded upon application start, so you can search right away, even while the new index is being built. This is already supported and part of the stable releases. > while i understand that indexing service is more complex job - at least caching the index would be nice, because right now when i start the app i have to wait for it to index everything again, but usually i search for files that exists for a long time, not these that was created between my fsearch uses Once the old feature set is working again, I'll publish the first official dev builds of the 0.3 release. loading/saving the database file is broken at the moment). ![]() That feature is already implemented, but there are no official builds with it yet, because other parts of the software haven't been updated after the rewrite of the database engine (e.g. > - being able to just remove a file from the index if you delete it from the app directly (insted it shows a window how it "soon" gonna be implemented) Though it's still months away from being released. I'm still working on it - not as often as I'd like to, but I'm still making progress towards the next release. ![]() > Also this is anbandoned apparently, which makes me extra sad, because it lacks few crucial features like: Hi, I'm the author of this little piece of software.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |