From: merlyn@stonehenge.com (Randal L. Schwartz)
To: ding@gnus.org
Subject: Re: odd behavior of gnus-summary-kill-thread
Date: Thu, 27 Jan 2011 18:13:00 -0800 [thread overview]
Message-ID: <86r5bx93o3.fsf@red.stonehenge.com> (raw)
In-Reply-To: <87wrlr6s75.fsf@gnus.org> (Lars Ingebrigtsen's message of "Wed, 26 Jan 2011 17:39:10 -0800")
>>>>> "Lars" == Lars Ingebrigtsen <larsi@gnus.org> writes:
Lars> But I'm not seeing this no matter what the setting of that
Lars> variable is.
Yeah, so maybe that's a red herring too.
Is there anything I can do to have this do the right thing, even when
the thread is folded?
--
Randal L. Schwartz - Stonehenge Consulting Services, Inc. - +1 503 777 0095
<merlyn@stonehenge.com> <URL:http://www.stonehenge.com/merlyn/>
Smalltalk/Perl/Unix consulting, Technical writing, Comedy, etc. etc.
See http://methodsandmessages.posterous.com/ for Smalltalk discussion
next prev parent reply other threads:[~2011-01-28 2:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-27 0:05 Randal L. Schwartz
2011-01-27 0:29 ` Randal L. Schwartz
2011-01-27 1:39 ` Lars Ingebrigtsen
2011-01-28 2:13 ` Randal L. Schwartz [this message]
2011-01-28 2:19 ` Lars Ingebrigtsen
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=86r5bx93o3.fsf@red.stonehenge.com \
--to=merlyn@stonehenge.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).