Open kergoth opened 7 years ago
@kergoth
Thanks for feedback. Lepton uses "lazy loading" for gists, which means the gist content is not fetched until users click on it. This mechanism limits the local search's capability, since it can only search for what has been downloaded.
The next release(the coming weekend) will have a big improvement on the search quality, like fuzzy search and unicode support. But as I just mentioned, I haven't come up with a good solution for content search yet.
All suggestions or PR will be welcome:)
P.S. GistBox is a cool project, but its development seems to be slow recently. That's one of reasons I start a new project for Gist.
Fair enough, I figured the fetching was the issue, as I'm guessing the gist api doesn't provide content search. Thanks for the quick reply, I look forward to playing with Lepton more, you've done nice work so far. It's a shame github's built in gist UI is so limited, particularly for those of us with a lot of gists :)
+1
Still a highly desired feature.
+1 this drastically limits the functionality of this otherwise super cool app.
I'd prefer a toggle or button that went ahead and forced a download of all gists so that we could do content search.
In other words, search continued to just search description and filename, but we could force it to go ahead and download everything so it could be searched.
Since gists are mostly text, it will not take much storage space to download them all. I guess full text search on the cached gists would be a good choice.
I just cannot beleive there is not a single tool which supports searching through the contents of your gists. How hard should it be to download all gists throught the GutHub API, put them in an sqllite file and do some good old information retreival?!?
+1 This feauter is really required. I would also agree that text files should not take to much space.
Github support search content via in:file
, can we utilize it?
It'd be nice if the search covered more than just description/filename, as quite often what I'm looking for is a command inside a shell script or something :) For example, GistBox supports this (though has other weaknesses, i.e. the tags are local to the app, not stored in the gists).