From: Eric Wong <e@80x24.org>
To: ruby-talk@ruby-lang.org, msgthr-public@80x24.org
Cc: misc@80x24.org
Subject: [ANN] msgthr 1.1.0 - container-agnostic, non-recursive message threading
Date: Sun, 31 Dec 2017 23:12:29 +0000 [thread overview]
Message-ID: <20171231231229.GA15335@dcvr> (raw)
Pure Ruby message threading based on the algorithm described by
JWZ in <https://www.jwz.org/doc/threading.html> and used in
countless mail and news readers; but with some features removed
and improved flexibility for non-mail/news usage.
* https://80x24.org/msgthr/README
* API: https://80x24.org/msgthr/rdoc/Msgthr.html
* public list: msgthr-public@80x24.org
* mail archives: https://80x24.org/msgthr-public/
* git clone https://80x24.org/msgthr.git
* follow releases: https://80x24.org/msgthr/NEWS.atom.xml
* follow all: https://80x24.org/msgthr-public/new.atom
* nntp://news.public-inbox.org/inbox.comp.lang.ruby.msgthr
Changes: msgthr 1.1.0 - simplify usage
This release simplifies the API to avoid (and raise on) user
errors. If your code worked with previous versions, there
are no changes necessary to make.
This release fixes our API to match the documentation in making
Msgthr#order! optional. Furthermore, the block previously
passed to Msgthr#order! may now be passed to Msgthr#thread!
instead.
For users who truly do not care about ordering, Msgthr#walk_thread
may be called immediately after the last call to Msgthr#add.
Thanks to Dimid Duchovny for the feedback which led to this release:
https://80x24.org/msgthr-public/CANKvuDc2mkxLuh+3+WXWfMXzxK2bShNesrD5xLocGOD1RybbwQ@mail.gmail.com/
--
https://80x24.org/msgthr/README
reply other threads:[~2017-12-31 23:12 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20171231231229.GA15335@dcvr \
--to=e@80x24.org \
--cc=misc@80x24.org \
--cc=msgthr-public@80x24.org \
--cc=ruby-talk@ruby-lang.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 read-only IMAP folder(s) and NNTP newsgroup(s).