Re: A lot of questions concerning `gnus-score-edit-file-at-point'

[sigurd@12move.de (Karl Pflästerer)]

On 30 Dec 2003, Reiner Steib <- 4.uce.03.r.s@nurfuerspam.de wrote:

> On Tue, Dec 30 2003, Karl Pflästerer wrote:

>> (defvar gnus-score-trace-format-alist
>>   (list ;; name            format string     regexp    
>>    (cons 'newformat (cons "%S [%s] -> %s\n" "-> +"))
>>    (cons 'oldformat (cons "%S -> %3$s\n"    "-> +"))))

> I don't understand the aim behind `gnus-score-trace-format-alist' in
> your code.  If 'newformat (or 'oldformat) is hard-coded in the
> relevant functions, I see no need for the variable.

If you use that var you asure that the two functions use the right pair
of format string and regexp.

As I wrote: best would be to have a second var which holds the name of
the key.

> We could use a variable to hold the delimiters (and maybe regexps?):

I don't see the difference to what I wrote.

> ("@my-fqdn>$" 10000 nil r) [my-posts] ->  ~/News/score/topics/my-posts.SCORE
> ^^^^^^^^^^^^^^^^^^^^^^^^^^--^^^^^^^^_^^^^^----------------------------------
> (a)                        |  (c)   | (e)             (f)
>                           (b)      (d)

> (a) the score rule
> (b) opening delimiter for (c)
> (c) abbreviated score file name (w/o directory and extension)
> (d) closing delimiter for (c)
> (e) separator (needed in `gnus-score-edit-file-at-point')
> (f) full name of the score file

> (b), (d) and (e) could be in the variable (alist).
> `gnus-score-edit-file-at-point' and `gnus-score-find-trace' use this
> variable.

The same as I proposed.  But with my proposal it's easy to add and use
new formats.

You would have two new vars:
`gnus-score-trace-format-alist' and `gnus-score-trace-format'.  The
later one has eg. 'oldformat as value.  Everywhere you see at the moment
oldformat that var could be used.  With that you are free to create
fancy formats.  Only the rule must be first and the long file name last
on the line.




   KP

-- 
"Programs must be written for people to read, and only incidentally
for machines to execute."
                -- Abelson & Sussman, SICP (preface to the first edition)