[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Nmh-workers] [PATCH] scan message numbers from stdin
From: |
Robert Elz |
Subject: |
Re: [Nmh-workers] [PATCH] scan message numbers from stdin |
Date: |
Sat, 16 Aug 2008 08:48:29 +0700 |
I'm not sure this is a great idea.
Fairly trivially, as documented in the proposed manual update, it
implies that
echo 1 2 3 4 5 | scan -
would be the same as
scan 1 2 3 4 5
but that isn't what the implementation does. Whether it should or
not I'm not sure, it would be convenient (if this is done at all),
but it isn't needed to handle output from pick, if that's the sole objective.
I'm also not sure that it's really worth optimising this all that much.
I have some huge folders (100K messages - just under I use %5d for my
scan format message numbers, so I move messages around when they approach 100K)
and pick isn't all that slow.
What's more, if it is, then you really want the results in a sequence,
all of them, so you're not relying on guessing correctly when you
interrupt things, and then having to start all over again when you
realise you're wrong. pick once, then scan as many times as needed
(I tend to pick, then scan +sel|grep when there's going to be enough for
any of this to make much sense - repeating the scan until the right
message is found is fast).
kre
- [Nmh-workers] [PATCH] scan message numbers from stdin, Eric Gillespie, 2008/08/15
- Re: [Nmh-workers] [PATCH] scan message numbers from stdin,
Robert Elz <=
- Re: [Nmh-workers] [PATCH] scan message numbers from stdin, Eric Gillespie, 2008/08/18
- Re: [Nmh-workers] [PATCH] scan message numbers from stdin, Peter Maydell, 2008/08/18
- Re: [Nmh-workers] [PATCH] scan message numbers from stdin, Eric Gillespie, 2008/08/19
- Re: [Nmh-workers] [PATCH] scan message numbers from stdin, Simon Burge, 2008/08/19
- Re: [Nmh-workers] [PATCH] scan message numbers from stdin, Paul Fox, 2008/08/19