From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.general/61624 Path: news.gmane.org!not-for-mail From: Katsumi Yamaoka Newsgroups: gmane.emacs.w3m,gmane.emacs.gnus.general Subject: [emacs-w3m:08485] Re: nnrss should borrow nnshibmun's RSS date processor...or something Date: Wed, 04 Jan 2006 11:13:44 +0900 Message-ID: References: <87y82dokdt.fsf@stone.tss.usg.edu> <8764p2g0wc.fsf@stone.tss.usg.edu> Reply-To: emacs-w3m@namazu.org NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: sea.gmane.org 1136340850 19455 80.91.229.2 (4 Jan 2006 02:14:10 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Wed, 4 Jan 2006 02:14:10 +0000 (UTC) Cc: emacs-w3m@namazu.org Original-X-From: emacs-w3m-admin@namazu.org Wed Jan 04 03:14:09 2006 Return-path: Envelope-to: emacs-w3m@deer.gmane.org Original-Received: from quimby.gnus.org ([80.91.224.244]) by ciao.gmane.org with esmtp (Exim 4.43) id 1EtyA4-0002ym-Fj for emacs-w3m@deer.gmane.org; Wed, 04 Jan 2006 03:14:00 +0100 Original-Received: from vaj.namazu.org ([61.215.208.42]) by quimby.gnus.org with esmtp (Exim 3.35 #1 (Debian)) id 1EtyA3-0002Sa-00 for ; Wed, 04 Jan 2006 03:14:00 +0100 Original-Received: from vaj.namazu.org (localhost [127.0.0.1]) by vaj.namazu.org (Postfix) with ESMTP id B95BB2012D; Wed, 4 Jan 2006 11:13:53 +0900 (JST) Original-Received: from washington.hostforweb.net (washington.hostforweb.net [66.225.201.13]) by vaj.namazu.org (Postfix) with ESMTP id 7FA24200D4 for ; Wed, 4 Jan 2006 11:13:52 +0900 (JST) Original-Received: from softbank218118002045.bbtec.net ([218.118.2.45]:65139 helo=) by washington.hostforweb.net with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.52) id 1EtyA5-0003gD-3M; Tue, 03 Jan 2006 20:14:01 -0600 Original-To: ding@gnus.org X-ML-Name: emacs-w3m X-Mail-Count: 08485 X-MLServer: fml [fml 4.0.3 release (20011202/4.0.3)]; post only (anyone can post) X-ML-Info: If you have a question, send e-mail with the body "help" (without quotes) to the address emacs-w3m-ctl@namazu.org; help= User-Agent: Gnus/5.110004 (No Gnus v0.4) Emacs/22.0.50 (gnu/linux) X-Face: #kKnN,xUnmKia.'[pp`;Omh}odZK)?7wQSl"4o04=EixTF+V[""w~iNbM9ZL+.b*_CxUmFk B#Fu[*?MZZH@IkN:!"\w%I_zt>[$nm7nQosZ<3eu;B:$Q_:p!',P.c0-_Cy[dz4oIpw0ESA^D*1Lw= L&i*6&( Cancel-Lock: sha1:CRz+uOJaacmr4Qd+1Xn9dff6XgE= X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - washington.hostforweb.net X-AntiAbuse: Original Domain - namazu.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - jpl.org X-Source: X-Source-Args: X-Source-Dir: X-Spam-Flag: No X-Spam-Probability: 0.000000 Precedence: bulk Original-Lines: 58 List-Id: emacs-w3m.namazu.org List-Software: fml [fml 4.0.3 release (20011202/4.0.3)] List-Post: List-Owner: List-Help: List-Unsubscribe: Xref: news.gmane.org gmane.emacs.w3m:5846 gmane.emacs.gnus.general:61624 Archived-At: >>>>> In [emacs-w3m : No.08484] >>>>> Mark Plaksin wrote: > Here's one way to include the newer timezone-parse-date but it looks ugly > and the Elisp docs say "In general, well-designed Lisp programs should not > use this feature [eval-after-load]." > (if (< emacs-major-version 22) > (eval-after-load "timezone" > '(defun timezone-parse-date (date) > ... ;; include definition from Emacs 22 > ))) This is similar to the way of APEL, with which I don't fully agree. One of the reasons is that it only hides imperfectness of certain Emacs versions. > Is there a better way or a better plan? I think the best way at the present is yours, i.e., to make nnrss always provide RFC822 date. However, I still don't know the reason why we should not use ISO 8601 date in nnrss articles. Though we might not be getting used to seeing it in our eyes, I don't think that is so serious. > If Gnus switches to date-to-time, then no change will be needed in nnrss, > yes? It will make several date-oriented features of Gnus, e.g., sorting, expiration, etc., work with ISO 8601 date. However, I'm not sure whether all those features actually work and are actually used. I can only say with certainty that they will work with RFC822 date. > I copied shimbun-rss-process-date, changed the first line from this: > (luna-define-method shimbun-rss-process-date ((shimbun shimbun-rss) date) > to this: > (defun map-shimbun-rss-date (date) > and then patched nnrss.el with the attached patch. Thanks. It looks good to me, and I seem to be able to rewrite it in nnrss.el if we cannot use the shimbun code directly. >> BTW, why do you prefer RFC822 date rather than ISO 8601 date? >> If it is for the bugfix, we should apply it to both the Gnus >> trunk and the v5-10 branch. > I don't know enough to prefer either format :) I was just trying to find a > way to make nnrss show the correct date all the time. Making nnrss able to > do this in both the trunk and v5-10 sounds good to me though I only use > trunk. Does ISO 8601 date actually cause you pain, or give you any trouble? If so, we can call it a bug and we should fix it. ;-)