From: marcus-sup@bar-coded.net (Marcus Williams)
Subject: [sup-talk] Should '/' trigger the loading of more messages?
Date: Thu, 27 Aug 2009 10:05:13 +0100 [thread overview]
Message-ID: <1251363903-sup-2197@bar-coded.net> (raw)
In-Reply-To: <1251340454-sup-3773@cannonball>
On 27.8.2009, Ingmar Vanhassel wrote:
> > What just happened to me is that I *knew* my inbox contained a message
> > with a particular string in the subject, but I couldn't find it with
> > '/'. The problem was that enough new threads had arrived that the
> > message of interest wasn't loaded yet.
>
> If you know it's in your inbox, why not search with '\', for
> 'label:inbox foo'?
... coupled with '!!' to load all threads in the search (ctrl-g works
to stop search) this would do what you want.
HTH
Marcus
next prev parent reply other threads:[~2009-08-27 9:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-26 22:47 Carl Worth
2009-08-27 2:37 ` Ingmar Vanhassel
2009-08-27 9:05 ` Marcus Williams [this message]
2009-08-27 12:17 ` Carl Worth
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=1251363903-sup-2197@bar-coded.net \
--to=marcus-sup@bar-coded.net \
/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