From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.general/32435 Path: main.gmane.org!not-for-mail From: Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai =?iso-8859-1?q?Gro=DFjohann?=) Newsgroups: gmane.emacs.gnus.general Subject: Re: Recommendations for paragraph filling within Gnus. Date: 15 Sep 2000 00:51:25 +0200 Sender: owner-ding@hpc.uh.edu Message-ID: References: <200009142153.WAA27649@djlvig.dl.ac.uk> NNTP-Posting-Host: coloc-standby.netfonds.no Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable X-Trace: main.gmane.org 1035168723 19817 80.91.224.250 (21 Oct 2002 02:52:03 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Mon, 21 Oct 2002 02:52:03 +0000 (UTC) Cc: ding@gnus.org Return-Path: Original-Received: from fisher.math.uh.edu (fisher.math.uh.edu [129.7.128.35]) by mailhost.sclp.com (Postfix) with ESMTP id 90108D051E for ; Thu, 14 Sep 2000 18:55:58 -0400 (EDT) Original-Received: from sina.hpc.uh.edu (lists@Sina.HPC.UH.EDU [129.7.3.5]) by fisher.math.uh.edu (8.9.1/8.9.1) with ESMTP id RAC12219; Thu, 14 Sep 2000 17:51:55 -0500 (CDT) Original-Received: by sina.hpc.uh.edu (TLB v0.09a (1.20 tibbs 1996/10/09 22:03:07)); Thu, 14 Sep 2000 17:51:15 -0500 (CDT) Original-Received: from mailhost.sclp.com (postfix@66-209.196.61.interliant.com [209.196.61.66] (may be forged)) by sina.hpc.uh.edu (8.9.3/8.9.3) with ESMTP id RAA16079 for ; Thu, 14 Sep 2000 17:51:03 -0500 (CDT) Original-Received: from waldorf.cs.uni-dortmund.de (waldorf.cs.uni-dortmund.de [129.217.4.42]) by mailhost.sclp.com (Postfix) with ESMTP id B84DAD051E for ; Thu, 14 Sep 2000 18:51:28 -0400 (EDT) Original-Received: from marcy.cs.uni-dortmund.de (marcy.cs.uni-dortmund.de [129.217.20.159]) by waldorf.cs.uni-dortmund.de with ESMTP id AAA26261; Fri, 15 Sep 2000 00:51:26 +0200 (MES) Original-Received: from lucy.cs.uni-dortmund.de (lucy [129.217.20.160]) by marcy.cs.uni-dortmund.de id AAA08236; Fri, 15 Sep 2000 00:51:26 +0200 (MET DST) Original-Received: (from grossjoh@localhost) by lucy.cs.uni-dortmund.de (8.9.3/8.9.3/Debian 8.9.3-21) id AAA10731; Fri, 15 Sep 2000 00:51:26 +0200 Original-To: Dave Love In-Reply-To: Dave Love's message of "Thu, 14 Sep 2000 22:53:50 +0100" User-Agent: Gnus/5.0808 (Gnus v5.8.8) Emacs/21.0.90 Original-Lines: 71 Precedence: list X-Majordomo: 1.94.jlt7 Xref: main.gmane.org gmane.emacs.gnus.general:32435 X-Report-Spam: http://spam.gmane.org/gmane.emacs.gnus.general:32435 On Thu, 14 Sep 2000, Dave Love wrote: >>>>>> "KG" =3D=3D Kai Gro=DFjohann >>>>>> writes: >=20 > KG> For example, message-mode has a method for determining the > KG> citation prefix for font-locking, and article-mode has a method > KG> for determining the citation prefix for highlighting, and they > KG> are different. >=20 > Is it clear whether or why this can't be done straightforwardly with > adaptive filling? Hm. I think the issue at hand is font-locking, which can't be done with filling. But of course, the adaptive fill regexp should be the same as the other regexps. I found these two snippets from gnus-cite.el and message.el, respectively: /---- | (defcustom gnus-cite-prefix-regexp | "^[]>=BB|:}+ ]*[]>=BB|:}+]\\(.*>=BB\\)?\\|^.*>" | "*Regexp matching the longest possible citation prefix on a line." | :group 'gnus-cite | :type 'regexp) \---- /---- | (defvar message-font-lock-keywords | (let* ((cite-prefix "A-Za-z") | (cite-suffix (concat cite-prefix "0-9_.@-")) | (content "[ \t]*\\(.+\\(\n[ \t].*\\)*\\)")) | `( | [...] | (,(concat "^[ \t]*" | "\\([" cite-prefix "]+[" cite-suffix "]*\\)?" | "[:>|}].*") | (0 'message-cited-text-face)) | ("<#/?\\(multipart\\|part\\|external\\|mml\\).*>" | (0 'message-mml-face)))) | "Additional expressions to highlight in Message mode.") \---- /----[ from the function message-mode ] | (setq adaptive-fill-regexp | (concat "[ \t]*[-a-z0-9A-Z]*\\(>[ \t]*\\)+[ \t]*\\|" adaptive-fill-regex= p)) \---- A large number of questions arise: * Why is =BB included in one but not the other regexp? * Suppose the citation prefix is `foo>', then gnus-cite allows a lot of characters before the `>', but message only allows letters and numbers and a few others. Why is this so? * The whole structure of the regexps is different. Wonder why? * Why is the set of characters `:>|}' not customizable (easily) in message.el?=20 * Why does message-mode assume that adaptive-fill-regexp will be fine for most citations and only adds to it for supercite-style citations? I'm sure that we could come up with more questions. This seems to be one of the dustier corners of Gnus... kai --=20 I like BOTH kinds of music.