From: Ted Zlatanov <tzz@lifelogs.com>
To: ding@gnus.org
Subject: Re: [PATCH] Make saving and restoring of hidden threads work with overlays.
Date: Thu, 12 Aug 2010 15:47:33 -0500 [thread overview]
Message-ID: <87mxsrimmy.fsf@lifelogs.com> (raw)
In-Reply-To: <b4mwrs76uzo.fsf@jpl.org>
On Wed, 04 Aug 2010 10:12:59 +0900 Katsumi Yamaoka <yamaoka@jpl.org> wrote:
KY> Ted Zlatanov wrote:
>> On Fri, 30 Jul 2010 17:47:49 +0100 Lawrence Mitchell <wence@gmx.li> wrote:
LM> * gnus-sum.el (gnus-hidden-threads-configuration)
LM> (gnus-restore-hidden-threads-configuration): Update to deal with text
LM> properties, rather than searching for a magic character.
>> Thank you for your contribution. It's a small change so I don't believe
>> you need papers on file. Can someone please test this against XEmacs?
KY> Tested it with XEmacs briefly. Works fine (the hidden thread is
KY> left hidden).
I comitted this today.
Ted
next prev parent reply other threads:[~2010-08-12 20:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-30 16:47 Lawrence Mitchell
2010-08-03 18:52 ` Ted Zlatanov
2010-08-04 1:12 ` Katsumi Yamaoka
2010-08-12 20:47 ` Ted Zlatanov [this message]
2010-08-04 8:23 ` Lawrence Mitchell
2010-08-04 11:08 ` Tassilo Horn
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=87mxsrimmy.fsf@lifelogs.com \
--to=tzz@lifelogs.com \
--cc=ding@gnus.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).