From: Dave Goldberg <david.goldberg6@verizon.net>
To: ding@gnus.org
Subject: Re: gnus-summary-limit-to-unread should document its antidote
Date: Mon, 21 Jul 2008 06:39:27 -0400 [thread overview]
Message-ID: <84prp7seqo.fsf@incoming.verizon.net> (raw)
In-Reply-To: <87y73w4efz.fsf@marauder.physik.uni-ulm.de> (Reiner Steib's message of "Sun, 20 Jul 2008 20:07:28 +0200")
>>>>> On Sun, 20 Jul 2008 20:07:28 +0200, Reiner Steib <reinersteib+gmane@imap.cc> /U7=m^"/-Dn61mAl{g9e3>\G5Tp,oEX|V)g2I1hBk\ML;)7A?6cmB-y7y?'NA^J<=oz7syB =(McAwIHgLX!.B?R3X}98d@?>CrT094KLWh]WU4gDpnL/")MS(XoQTv`Oq225uL>+;CpPXo$N5e>N> $tPd-gbB^F{gQS#1ase]XO~D4p4M"3+F-7~u]dy3I?Pb8RO*H-EFeWDUf?Rf,d]pv\Jvh2Cht!A=im yKAS2Z%Ao^;}W/qzMvMm said:
> On Sun, Jul 20 2008, jidanni@jidanni.org wrote:
>> x runs the command gnus-summary-limit-to-unread.
>> Its docstring should mention its antidote.
> I don't think there's an exact antidote for `x'. `/ o' surely isn't it.
What about `/ w'? gnus-summary-pop-limit.
--
Dave Goldberg
david.goldberg6@verizon.net
next prev parent reply other threads:[~2008-07-21 10:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-20 13:28 jidanni
2008-07-20 18:07 ` Reiner Steib
2008-07-21 10:39 ` Dave Goldberg [this message]
2008-07-21 20:26 ` Reiner Steib
2008-07-21 10:39 ` Johan Bockgård
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=84prp7seqo.fsf@incoming.verizon.net \
--to=david.goldberg6@verizon.net \
--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).