From: Thien-Thi Nguyen <ttn@gnu.org>
To: Alex Schroeder <alex@gnu.org>
Cc: info-gnus-english@gnu.org
Subject: Re: Deleting duplicates from nnml:mail.misc
Date: Mon, 14 Oct 2013 09:16:52 +0200 [thread overview]
Message-ID: <878uxwz5i3.fsf@zigzag.favinet> (raw)
In-Reply-To: <m27gdhdn8e.fsf@gnu.org> (Alex Schroeder's message of "Sun, 13 Oct 2013 20:44:49 +0200")
[-- Attachment #1.1: Type: text/plain, Size: 438 bytes --]
() Alex Schroeder <alex@gnu.org>
() Sun, 13 Oct 2013 20:44:49 +0200
And it takes long seconds to build up the data structures.
If order does not matter, you can use a hash table instead of an alist.
--
Thien-Thi Nguyen
GPG key: 4C807502
(if you're human and you know it)
read my lisp: (responsep (questions 'technical)
(not (via 'mailing-list)))
=> nil
[-- Attachment #1.2: Type: application/pgp-signature, Size: 197 bytes --]
[-- Attachment #2: Type: text/plain, Size: 162 bytes --]
_______________________________________________
info-gnus-english mailing list
info-gnus-english@gnu.org
https://lists.gnu.org/mailman/listinfo/info-gnus-english
prev parent reply other threads:[~2013-10-14 7:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-07 23:00 Alex Schroeder
2013-10-13 18:44 ` Alex Schroeder
2013-10-14 7:16 ` Thien-Thi Nguyen [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=878uxwz5i3.fsf@zigzag.favinet \
--to=ttn@gnu.org \
--cc=alex@gnu.org \
--cc=info-gnus-english@gnu.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).