From: Richard Riley <rileyrg@googlemail.com>
To: info-gnus-english@gnu.org
Subject: Re: Today's articles/mails..
Date: Tue, 21 Dec 2010 14:26:01 +0100 [thread overview]
Message-ID: <ieq9t9$1gp$1@quimby.gnus.org> (raw)
In-Reply-To: <mailman.1.1292937453.31822.info-gnus-english@gnu.org>
Tassilo Horn <tassilo@member.fsf.org> writes:
> Richard Riley <rileyrg@googlemail.com> writes:
>
> Hi Rich,
>
>>> ,----[ (info "(gnus)Limiting") ]
>>> | `/ w'
>>> | Pop the previous limit off the stack and restore it
>>> | (`gnus-summary-pop-limit'). If given a prefix, pop all limits off
>>> | the stack.
>>> `----
>>
>>
>> It would be nice (or is there) to have a variable to disable this :
>
> Hm, that would mean losing the ability of limiting with different
> concerns, like limiting to articles from Richard received the last 30
> days.
This true but normally (99%) of the time I only filter on last day or
name. Rarely both so the default for me would be better not to stack.
>
>> personally I never want the limits stacked and would like my next one
>> to override the previous rather than having to manually pop the limit
>> first.
>
> I think you could advice all gnus-summary-limit-* commands to do a
> (gnus-summary-pop-limit t) before, but that's a bit ugly IMHO.
>
> Bye,
> Tassilo
>
> Sent from my Emacs
>
--
☘ http://www.shamrockirishbar.com, http://splash-of-open-sauce.blogspot.com/ http://www.richardriley.net
prev parent reply other threads:[~2010-12-21 13:26 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-21 3:08 bgmrao
2010-12-21 10:28 ` Tassilo Horn
2010-12-21 13:16 ` bgmrao
2010-12-21 13:26 ` Tassilo Horn
2010-12-21 13:37 ` Andrew Cohen
2010-12-21 14:35 ` bgmrao
2010-12-21 14:40 ` Andrew Cohen
2010-12-21 14:57 ` Tassilo Horn
[not found] ` <mailman.15.1292927362.19366.info-gnus-english@gnu.org>
2010-12-21 11:46 ` Richard Riley
2010-12-21 13:17 ` Tassilo Horn
[not found] ` <mailman.1.1292937453.31822.info-gnus-english@gnu.org>
2010-12-21 13:26 ` Richard Riley [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='ieq9t9$1gp$1@quimby.gnus.org' \
--to=rileyrg@googlemail.com \
--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).