From mboxrd@z Thu Jan  1 00:00:00 1970
X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.user/1875
Path: news.gmane.org!not-for-mail
From: Francois-David.Collin@wanadoo.fr (=?iso-8859-1?q?Fran=E7ois-David?=
 Collin)
Newsgroups: gmane.emacs.gnus.user
Subject: Re: [REQ] Feature Request : "fancy" gnus-posting-styles
Date: Tue, 14 Jan 2003 08:28:49 +0100
Message-ID: <uy95ofavi.fsf@wanadoo.fr>
References: <uvg0t1f1m.fsf@wanadoo.fr> <m31y3gudaz.fsf@quimbies.gnus.org>
NNTP-Posting-Host: main.gmane.org
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Trace: sea.gmane.org 1138668509 13029 80.91.229.2 (31 Jan 2006 00:48:29 GMT)
X-Complaints-To: usenet@sea.gmane.org
NNTP-Posting-Date: Tue, 31 Jan 2006 00:48:29 +0000 (UTC)
Original-X-From: nobody Tue Jan 17 17:29:50 2006
Original-Path: quimby.gnus.org!not-for-mail
Original-Newsgroups: gnu.emacs.gnus
Original-NNTP-Posting-Host: xlate2-90.curie.fr
Original-X-Trace: quimby.gnus.org 1042529738 8344 195.220.102.90 (14 Jan 2003 07:35:38 GMT)
Original-X-Complaints-To: usenet@quimby.gnus.org
Original-NNTP-Posting-Date: 14 Jan 2003 07:35:38 GMT
X-Home-Page: http://perso.curie.fr/fradav
X-Attribution: fd
User-Agent: Gnus/5.090013 (Oort Gnus v0.13) Emacs/21.2
 (i386-msvc-nt5.1.2600)
Cancel-Lock: sha1:UGVehw+zt4lZVxdiOnK2G8T2uHY=
Original-Xref: bridgekeeper.physik.uni-ulm.de gnus-emacs-gnus:2015
Original-Lines: 37
X-Gnus-Article-Number: 2015   Tue Jan 17 17:29:50 2006
Xref: news.gmane.org gmane.emacs.gnus.user:1875
Archived-At: <http://permalink.gmane.org/gmane.emacs.gnus.user/1875>

>>>>> In article <m31y3gudaz.fsf@quimbies.gnus.org>,
>>>>> Lars Magne Ingebrigtsen <larsi@gnus.org> writes:


    Lars> I think it sounds like a good idea.  It could definitely be
    Lars> useful.

Well, after the countless posts in answer of mine, that's what we
could deduce :-)

So, let's go.

I looked at the function gnus-configure-posting-styles, and I realize
that I really don't want to touch it. To implement the thing, I'm
thinking, in a first approach, of a wrapper wich converts the tree in
a flat standard gnus-posting-styles, in short : for each leaf in the
tree, reached by a in-depth walk, we provide a boolean expression to
insert as a standard match the gnus-posting-styles, along with the
posting attributes of the leaf. This sounds undoubtfully familiar to
all the tree-algorithms-addicts we all are :-)


They're two drawbacks :

- the gnus-posting-style variable won't be human-readable, perhaps
  should be hidden

- if the tree is complex, the leaf expressions could be very long, the
  gnus-configure will slowly parses a very very big structure. I don't
  think we will encounter such a situation, but who knows. If speed
  matters, providing a global function which stores a walk-state in
  the tree, and using this function in match-clause of
  gnus-posting-styles should do the trick.

Comments?
-- 
F.-D.