On Wed, May 4, 2011 at 9:48 PM, Austin Clements wrote:
> As another data point, with a probably very different configuration (8
> year old P4, new SSD), my test query was 1.9X faster uncached and 1.6X
> faster cached. ?It also produced 60% fewer disk reads. ?I saw the same
> 1% increase in
This is awesome. What was your machine configuration?
As another data point, with a probably very different configuration (8
year old P4, new SSD), my test query was 1.9X faster uncached and 1.6X
faster cached. It also produced 60% fewer disk reads. I saw the same
1% increase in database size.
Quoth Felipe Contreras on May 04 at 11:54 pm:
> On Wed, May 4, 2011 at 11:46 PM, Austin Clements wrote:
> > On Wed, May 4, 2011 at 4:26 PM, Felipe Contreras
> > wrote:
> >> +output=$(notmuch search from:'search-by-from@' | notmuch_search_sanitize)
> >
> > I don't think this does what you think
On Wed, May 4, 2011 at 4:26 PM, Felipe Contreras
wrote:
> +output=$(notmuch search from:'search-by-from@' | notmuch_search_sanitize)
I don't think this does what you think it does. Xapian only
understands double quotes around phrases, not single quotes.
Furthermore, a single quote after a
This tests notmuch new's ability to recover from arbitrary stopping
failures. It interrupts notmuch new after every database commit and,
on every resulting database snapshot, re-runs notmuch new to
completion and checks that the final database state is invariant.
---
This addresses a timing bug
jrollins found a timing bug in the atomicity test. A fix, plus beefed
up test comments are on a new atomic-new-v3 (and
for-review/atomic-new-v3) branch at
http://awakening.csail.mit.edu/git/notmuch.git/
Since this is more than a rebase, I'll email an update to the one
changed patch in the
On Tue, Apr 5, 2011 at 8:46 AM, Jeff Richards j...@jrichards.ca wrote:
On Mon, 4 Apr 2011 18:56:52 +0300, Felipe Contreras
felipe.contre...@gmail.com wrote:
On Mon, Apr 4, 2011 at 4:38 AM, Jeff Richards j...@jrichards.ca wrote:
notmuch.vim plugin can use the d keybinding to remove 'inbox'
Signed-off-by: Felipe Contreras felipe.contre...@gmail.com
---
vim/plugin/notmuch.vim |6 ++
1 files changed, 6 insertions(+), 0 deletions(-)
diff --git a/vim/plugin/notmuch.vim b/vim/plugin/notmuch.vim
index 3375a96..05e4552 100644
--- a/vim/plugin/notmuch.vim
+++
Signed-off-by: Felipe Contreras felipe.contre...@gmail.com
---
vim/plugin/notmuch.vim |6 ++
1 files changed, 6 insertions(+), 0 deletions(-)
diff --git a/vim/plugin/notmuch.vim b/vim/plugin/notmuch.vim
index 6f9ff18..c49ada5 100644
--- a/vim/plugin/notmuch.vim
+++
Signed-off-by: Felipe Contreras felipe.contre...@gmail.com
---
vim/plugin/notmuch.vim |6 ++
1 files changed, 6 insertions(+), 0 deletions(-)
diff --git a/vim/plugin/notmuch.vim b/vim/plugin/notmuch.vim
index 05e4552..6f9ff18 100644
--- a/vim/plugin/notmuch.vim
+++
This tests notmuch new's ability to recover from arbitrary stopping
failures. It interrupts notmuch new after every database commit and,
on every resulting database snapshot, re-runs notmuch new to
completion and checks that the final database state is invariant.
---
This addresses a timing bug
On Wed, May 4, 2011 at 4:26 PM, Felipe Contreras
felipe.contre...@gmail.com wrote:
+output=$(notmuch search from:'search-by-from@' | notmuch_search_sanitize)
I don't think this does what you think it does. Xapian only
understands double quotes around phrases, not single quotes.
Furthermore, a
Quoth Felipe Contreras on May 04 at 11:54 pm:
On Wed, May 4, 2011 at 11:46 PM, Austin Clements amdra...@mit.edu wrote:
On Wed, May 4, 2011 at 4:26 PM, Felipe Contreras
felipe.contre...@gmail.com wrote:
+output=$(notmuch search from:'search-by-from@' | notmuch_search_sanitize)
I don't
It's not really tricky, there are many addresses with a '-' in them. I
personally really want to differentiate between f...@bar.com,
foo-test...@bar.com, and foo-patc...@bar.com.
This fails, but it shouldn't:
FAIL Search by from (tricky):
--- search.17.expected 2011-05-04
This is awesome. What was your machine configuration?
As another data point, with a probably very different configuration (8
year old P4, new SSD), my test query was 1.9X faster uncached and 1.6X
faster cached. It also produced 60% fewer disk reads. I saw the same
1% increase in database size.
On Wed, May 4, 2011 at 9:48 PM, Austin Clements amdra...@mit.edu wrote:
As another data point, with a probably very different configuration (8
year old P4, new SSD), my test query was 1.9X faster uncached and 1.6X
faster cached. It also produced 60% fewer disk reads. I saw the same
1%
16 matches
Mail list logo