Rick Moen wrote:
Some would argue slrn. I personally would say tin.[1]
OK, first serious problem: tin expects long threads with text/plain articles. gwene.net.lwn.headlines.newrss, for example, has single-article threads that each contain only a text/html attachment, so it looks like this: Thu, 17 Nov 2011 12:19:50 gwene.net.lwn.headlines.newrss Thread 1344 of 1344 Lines 6 [$] LWN.net Weekly Edition for November 17, 2011 No responses corbet <post@gwene.org> Newsgroups: gwene.net.lwn.headlines.newrss [-- text/html, encoding 8bit, charset: utf-8, 6 lines --] <n>=set current to n; <TAB>=next unread; /=search pattern; ^K=kill/select a=author search; B=body search; c=catchup; f=followup; K=mark read |=pipe; m=mail; o=print; q=quit; r=reply mail; s=save; t=tag; w=post -- Last response -- Gnus automagically shoved the text/html part through emacs-w3m. I don't suppose I can tell tin to do likewise for w3m? I can't see the equivalent of mutt's "v" to get to the attachment. Even if I find that I forsee that being a pain in the arse, because I'm used to just hitting space to go to the next unread article (if necessary, by going to the next unread thread or group first) -- tin seems to want me to do a lot of q's and ^M's, at least by default. Stupid RSS... I think this is enough of a showstopper that I'm going to need to stick with a newsreader that's hooked into a browser, so that I can follow all the <a href="useful url">this</a> tags that literally say "this" rather than something useful. Unless someone has already a working tinrc that just DTRT with w3m/lynx -dump and urlview or something? PS: the gmane (mailing list) bridge is considerably more sane PPS: on the plus side, tin tells me *up front* when a list is one-way, whereas gnus waits until after I've written the bloody reply.