From: Reiner Steib <4.uce.03.r.s@nurfuerspam.de>
Subject: Re: A lot of questions concerning `gnus-score-edit-file-at-point'
Date: Tue, 30 Dec 2003 21:58:23 +0100 [thread overview]
Message-ID: <v9llouf2fk.fsf@marauder.physik.uni-ulm.de> (raw)
In-Reply-To: <m38ykui5k8.fsf@hamster.pflaesterer.de>
On Tue, Dec 30 2003, Karl Pflästerer wrote:
> On 30 Dec 2003, Reiner Steib <- 4.uce.03.r.s@nurfuerspam.de wrote:
[...]
> 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.
This is because I didn't understand your proposal. ;-)
> 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.
Wouldn't it make more sense to defcustom
`gnus-score-trace-format-alist' and offer some predefined choices:
:type '(choice (const :tag "old style" ...)
(const :tag "news style" ...)
(const :tag "foo style" ...))
I have committed new versions of `gnus-score-edit-file-at-point' and
`gnus-score-find-trace' now. `gnus-score-edit-file-at-point' is your
latest version but without `gnus-score-trace-format-alist' (we may add
this later) and some minor modifications. `gnus-score-find-trace'
uses `dolist' as you suggested. I hope it's okay for you.
(You have signed copyright assignments, IIRC?)
Bye, Reiner.
--
,,,
(o o)
---ooO-(_)-Ooo--- PGP key available via WWW http://rsteib.home.pages.de/
next prev parent reply other threads:[~2003-12-30 20:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-28 17:45 Karl Pflästerer
2003-12-29 17:15 ` Reiner Steib
2003-12-29 19:59 ` Karl Pflästerer
2003-12-29 21:15 ` Reiner Steib
2003-12-29 23:10 ` Karl Pflästerer
2003-12-30 13:40 ` Reiner Steib
2003-12-30 17:30 ` Karl Pflästerer
2003-12-30 20:58 ` Reiner Steib [this message]
2003-12-30 21:17 ` Karl Pflästerer
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=v9llouf2fk.fsf@marauder.physik.uni-ulm.de \
--to=4.uce.03.r.s@nurfuerspam.de \
--cc=reiner.steib@gmx.de \
/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).