From: Lars Magne Ingebrigtsen <larsi@gnus.org>
Subject: Re: [REQ] Feature Request : "fancy" gnus-posting-styles
Date: Tue, 14 Jan 2003 19:03:53 +0100 [thread overview]
Message-ID: <m3znq3pq0m.fsf@quimbies.gnus.org> (raw)
In-Reply-To: <uy95ofavi.fsf@wanadoo.fr>
Francois-David.Collin@wanadoo.fr (François-David Collin) writes:
> 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,
[...]
> They're two drawbacks :
>
> - the gnus-posting-style variable won't be human-readable, perhaps
> should be hidden
That could be dealt with by adding an additional variable that this
complex spec would have control over, and letting
`gnus-configure-posting-styles' use that as well.
> - 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.
I think that might be a problem.
`gnus-configure-posting-styles' is a quite long function, but it
isn't all that complex. I think you should be able to shoe-horn in a
predicate-like spec in there without too much problem.
A third method would be to use `gnus-make-predicate' to just make a
function out of the predicates, but it might be difficult to make it
fit in there...
--
(domestic pets only, the antidote for overdose, milk.)
larsi@gnus.org * Lars Magne Ingebrigtsen
prev parent reply other threads:[~2003-01-14 18:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <uvg0t1f1m.fsf@wanadoo.fr>
[not found] ` <m31y3gudaz.fsf@quimbies.gnus.org>
2003-01-14 7:28 ` François-David Collin
2003-01-14 18:03 ` Lars Magne Ingebrigtsen [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m3znq3pq0m.fsf@quimbies.gnus.org \
--to=larsi@gnus.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).