[notmuch] Notmuch's search view sucks
Karl Wiberg wrote: > On Fri, Dec 4, 2009 at 1:29 AM, Carl Worth wrote: >> And a step beyond that would support different languages for >> different emails, but that sounds like something "hard" to identify. > > But probably not as hard as identifying spam. It could probably be > done with a simple Bayesian filter counting word frequencies---but > it'd be much better if somebody else had already solved the problem, > since this smells suspiciously like something that ought to be a > separate project and put in a library ... does anyone know if such a > project already exists? I know Google can do it ... > > It'd be very cool to have notmuch automatically tag messages according > to what language they're in. What we should have is an interface to run an external program to classify a message when it's newly introduced and another that runs when tags are changed so that machine learning can be made to work when the user changes tags. Baruch
[notmuch] semi-usable notmuch-gtk client
Bart Trojanowski wrote: > * Baruch Even [091127 12:58]: >> I added a quick hack to show a message thread in notmuch-gtk and this >> makes it semi-usable. I don't actually parse the reply of notmuch-show >> but it's already passably usable to read mail. > > got screenshots? I created them now at http://baruch.github.com/notmuch-gtk They are not pretty and not meant to be, I'm currently just tracing out the client to get it somewhat functional as a mail client. The niceties will come once I actually get to use it as properly. Baruch
[notmuch] semi-usable notmuch-gtk client
Hi, I added a quick hack to show a message thread in notmuch-gtk and this makes it semi-usable. I don't actually parse the reply of notmuch-show but it's already passably usable to read mail. Baruch
[notmuch] A gtk interface
Carl Worth wrote: > On Thu, 26 Nov 2009 21:17:33 +0200, Baruch Even wrote: >> I've started to work on a Gtk+ interface to notmuch which uses the >> notmuch command line. Currently it is able to search threads and retag >> them. Next on the agenda is the ability to actually read the threads. >> >> If someone is interested, the code lives in >> http://github.com/baruch/notmuch-gtk and can be checked out from >> git://github.com/baruch/notmuch-gtk.git > > Very interesting, Baruch! > > Thanks for contributing this! > > I thought at first that the tagging commands weren't working, but > quickly realized they were working but simply weren't updating the view > to show the added/removed tags. Yes. The UI has a lot of rough edges, the search needs to be cancelable, it needs to indicate that it's in progress and I also need to implement some logic to update the threads that were retagged. But I'm more interested in fleshing out the rest of the app to make it somewhat useful to me so I can start to really make use of it. > PS. I prefer a default search of "tag:inbox" rather than "tag:inbox and > tag:unread". Otherwise, there's not much reason for "notmuch new" to add > both tags. It was like that initially, I didn't even have a good reason to change it as I didn't have the ability to change tags. I'll probably change it back. Baruch
[notmuch] A gtk interface
Hi, I've started to work on a Gtk+ interface to notmuch which uses the notmuch command line. Currently it is able to search threads and retag them. Next on the agenda is the ability to actually read the threads. If someone is interested, the code lives in http://github.com/baruch/notmuch-gtk and can be checked out from git://github.com/baruch/notmuch-gtk.git The recent streaming changes made things smoother. Though tagging is excessively slow if done on a thread-by-thread basis as I implemented it now. Baruch