From: Reiner Steib <reinersteib+gmane@imap.cc>
Subject: message-remove-duplicates and gnus-remove-duplicates (was: Changes committed gnus/lisp (ChangeLog gnus-art.el message.el))
Date: Wed, 28 Sep 2005 16:25:25 +0200 [thread overview]
Message-ID: <v9zmpxs20a.fsf@marauder.physik.uni-ulm.de> (raw)
In-Reply-To: <E1EKH9h-0000UQ-00@quimby.gnus.org>
On Tue, Sep 27 2005, Simon Josefsson committed:
> 2005-09-27 Arne Jørgensen <arne@arnested.dk>
>
> * message.el (message-remove-duplicates): New function.
> Implementation borrowed from `gnus-remove-duplicates'.
[...]
> +(defun message-remove-duplicates (list)
> + (let (new)
> + (while list
> + (or (member (car list) new)
> + (setq new (cons (car list) new)))
> + (setq list (cdr list)))
> + (nreverse new)))
Shouldn't we drop (or defalias) `gnus-remove-duplicates' in favor of
`message-remove-duplicates'? (We can safely require `message.el' in
Gnus code but not the other way round.)
,----
| grep -nH -e "[se]-remove-duplicates" *.el
| gnus-util.el:1033:(defun gnus-remove-duplicates (list)
| message.el:2093:(defun message-remove-duplicates (list)
| message.el:5041: (message-remove-duplicates
| nnmail.el:1144: (setq split (gnus-remove-duplicates split))
`----
nnmail.el (the only use of gnus-remove-duplicates) already requires
message.
Bye, Reiner.
--
,,,
(o o)
---ooO-(_)-Ooo--- | PGP key available | http://rsteib.home.pages.de/
next parent reply other threads:[~2005-09-28 14:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1EKH9h-0000UQ-00@quimby.gnus.org>
2005-09-28 14:25 ` Reiner Steib [this message]
2005-09-29 13:39 ` message-remove-duplicates and gnus-remove-duplicates Simon Josefsson
2005-10-02 20:24 ` Reiner Steib
2005-10-03 8:38 ` Simon Josefsson
2005-10-03 10:51 ` Reiner Steib
2005-10-03 13:58 ` Simon Josefsson
2005-10-03 17:55 ` Reiner Steib
2005-10-04 10:01 ` Simon Josefsson
2005-10-04 15:50 ` Reiner Steib
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=v9zmpxs20a.fsf@marauder.physik.uni-ulm.de \
--to=reinersteib+gmane@imap.cc \
--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).