Gnus development mailing list
 help / color / mirror / Atom feed
From: XeCycle <xecycle@gmail.com>
To: Lars Magne Ingebrigtsen <larsi@gnus.org>
Cc: ding@gnus.org
Subject: Re: Limits: Use default value from current article?
Date: Mon, 11 Jun 2012 12:06:02 +0800	[thread overview]
Message-ID: <87r4tm8pcl.fsf@xc.laptop> (raw)
In-Reply-To: <m3txyjlyoe.fsf@stories.gnus.org> (Lars Magne Ingebrigtsen's message of "Sun, 10 Jun 2012 22:06:09 +0200")

[-- Attachment #1: Type: text/plain, Size: 1076 bytes --]

Lars Magne Ingebrigtsen <larsi@gnus.org> writes:

> XeCycle <XeCycle@Gmail.com> writes:
>
>> What about using the default value from current article?  E.g. I
>> maybe reading my mails and found I need to look for other mails
>> From this sender.  Thus I type /a, and I need to enter his name
>> --- why don't we use a default value taken from the current
>> article, thus I simply need to /a RET.
>
> Good idea.  I've now added this to Ma Gnus.

Thanks, I'll try them out.

>> Other commands could use this too, e.g. /t defaults to show
>> articles older than this one, /s defaults to show articles with
>> the same title as the current one.
>
> I'm not sure `/ s' sounds as useful...  And I'm not sure I see the use
> case for a default `/ t' value either.

Yeah, they doesn't look as useful.  If it were me, I'd add them
anyway.  It's a form of consistency in user interface.

-- 
Carl Lei (XeCycle)
Department of Physics, Shanghai Jiao Tong University
OpenPGP public key: 7795E591
Fingerprint: 1FB6 7F1F D45D F681 C845 27F7 8D71 8EC4 7795 E591

[-- Attachment #2: Type: application/pgp-signature, Size: 489 bytes --]

      reply	other threads:[~2012-06-11  4:06 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-01 10:43 XeCycle
2012-06-10 20:06 ` Lars Magne Ingebrigtsen
2012-06-11  4:06   ` XeCycle [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=87r4tm8pcl.fsf@xc.laptop \
    --to=xecycle@gmail.com \
    --cc=ding@gnus.org \
    --cc=larsi@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).