Hi :)
Olly wrote:
>It is hard to say if calling close() is actually useful here from just
>seeing the patch.
Huh? I provided a test case...
Quoting Austin Clements (2012-02-29 23:17:54)
>Quoth Olly Betts on Feb 29 at 9:19 pm:
>> On Wed, Feb 29, 2012 at 10:48:33AM -0500, Austin Clements wrote:
>
On Tue, 21 Feb 2012 10:15:08 +0100, Michal Sojka wrote:
> -- >8 --
> Subject: [PATCH] emacs: Clarify description of thread manipulating functions
>
> It is not clear whether the term "thread" refers to the thread in the
> database or to the thread currently shown in a buffer. Those two
> meanings
On Wed, Feb 29, 2012 at 10:48:33AM -0500, Austin Clements wrote:
> Quoth Justus Winter on Feb 29 at 10:19 am:
> > Formerly the xapian database object was deleted and closed in its
> > destructor once the object was garbage collected. Explicitly call
> > close() so that the database and the associat
Quoting Philippe LeCavalier (2012-02-29 16:31:40)
>I had nottoomuch-addresses.sh working perfectly in emacs and I'm trying
>to get it going in alot. Here's[1] what I've got so far. One things that
>really confusing me is the brackets in the help file[2]. As soon as I
>put double brackets alot can't
On Tue, 21 Feb 2012 10:15:08 +0100, Michal Sojka wrote:
> -- >8 --
> Subject: [PATCH] emacs: Clarify description of thread manipulating functions
>
> It is not clear whether the term "thread" refers to the thread in the
> database or to the thread currently shown in a buffer. Those two
> meanings
---
test/search |2 ++
1 files changed, 2 insertions(+), 0 deletions(-)
diff --git a/test/search b/test/search
index 414be35..c55522b 100755
--- a/test/search
+++ b/test/search
@@ -130,6 +130,7 @@ output=$(notmuch search "b?d?" | notmuch_search_sanitize)
test_expect_equal "$output" "thread:X
---
notmuch-count.c |8 +---
notmuch-search.c |8 +---
2 files changed, 2 insertions(+), 14 deletions(-)
diff --git a/notmuch-count.c b/notmuch-count.c
index 63459fb..f86cb40 100644
--- a/notmuch-count.c
+++ b/notmuch-count.c
@@ -35,9 +35,6 @@ notmuch_count_command (void *ctx, in
---
man/man1/notmuch-config.1 |8
1 files changed, 0 insertions(+), 8 deletions(-)
diff --git a/man/man1/notmuch-config.1 b/man/man1/notmuch-config.1
index 0260eb7..36e09f4 100644
--- a/man/man1/notmuch-config.1
+++ b/man/man1/notmuch-config.1
@@ -85,14 +85,6 @@ directory hierarchy.
---
NEWS | 18 --
1 files changed, 0 insertions(+), 18 deletions(-)
diff --git a/NEWS b/NEWS
index b2bec04..5fa8043 100644
--- a/NEWS
+++ b/NEWS
@@ -11,24 +11,6 @@ Reply to sender
to all. The feature is available through the new command line option
--reply-to=(all|sender).
This disables the addition of search_exclude_tags in notmuch-setup and
notmuch-config.
---
notmuch-config.c |3 +--
notmuch-setup.c | 19 +--
2 files changed, 2 insertions(+), 20 deletions(-)
diff --git a/notmuch-config.c b/notmuch-config.c
index e9b2750..61fda3e 100644
---
As requested by David (Bremner) on irc here is a patch series
disabling the search.exclude_tags feature as a temporary measure for
the 0.12 release.
There are two options:
The first is to disable the addition of the new search.exclude_tags
item to the config file and stop setup from asking for it
On Wed, 29 Feb 2012 10:50:46 -0500, Jesse Rosenthal
wrote:
> On Wed, 29 Feb 2012 10:36:57 -0500, Austin Clements
> wrote:
> > What if the output of search (say, specifically the JSON format)
> > included information on each message in the thread such as the
> > 'message' production from devel/s
Hi!
The config syntax changed recently, when I switched from configparser to
configobj.
To clarify:
* the new config syntax is explained in the user docs at http://alot.rtfd.org.
These are auto-generated at each commit and correspond to the `testing`
branch,
which is where the bleeding edge
Quoth Olly Betts on Feb 29 at 9:19 pm:
> On Wed, Feb 29, 2012 at 10:48:33AM -0500, Austin Clements wrote:
> > Quoth Justus Winter on Feb 29 at 10:19 am:
> > > Formerly the xapian database object was deleted and closed in its
> > > destructor once the object was garbage collected. Explicitly call
>
On Wed, 29 Feb 2012 10:50:46 -0500, Jesse Rosenthal wrote:
> On Wed, 29 Feb 2012 10:36:57 -0500, Austin Clements wrote:
> > What if the output of search (say, specifically the JSON format)
> > included information on each message in the thread such as the
> > 'message' production from devel/schem
Quoth Olly Betts on Feb 29 at 9:19 pm:
> On Wed, Feb 29, 2012 at 10:48:33AM -0500, Austin Clements wrote:
> > Quoth Justus Winter on Feb 29 at 10:19 am:
> > > Formerly the xapian database object was deleted and closed in its
> > > destructor once the object was garbage collected. Explicitly call
>
On Wed, Feb 29, 2012 at 10:48:33AM -0500, Austin Clements wrote:
> Quoth Justus Winter on Feb 29 at 10:19 am:
> > Formerly the xapian database object was deleted and closed in its
> > destructor once the object was garbage collected. Explicitly call
> > close() so that the database and the associat
Hi.
I had nottoomuch-addresses.sh working perfectly in emacs and I'm trying
to get it going in alot. Here's[1] what I've got so far. One things that
really confusing me is the brackets in the help file[2]. As soon as I
put double brackets alot can't read the account. Am I misunderstanding
somethi
Quoting Philippe LeCavalier (2012-02-29 16:31:40)
>I had nottoomuch-addresses.sh working perfectly in emacs and I'm trying
>to get it going in alot. Here's[1] what I've got so far. One things that
>really confusing me is the brackets in the help file[2]. As soon as I
>put double brackets alot can't
On Wed, 29 Feb 2012 10:36:57 -0500, Austin Clements wrote:
> What if the output of search (say, specifically the JSON format)
> included information on each message in the thread such as the
> 'message' production from devel/schemata minus the body field? Then
> the frontend would have loads of i
Quoth Justus Winter on Feb 29 at 10:19 am:
> Formerly the xapian database object was deleted and closed in its
> destructor once the object was garbage collected. Explicitly call
> close() so that the database and the associated lock is released
> immediately.
Interesting. Is this a bug in Xapian
Quoth Jesse Rosenthal on Feb 29 at 10:05 am:
> On Sun, 26 Feb 2012 16:59:53 -0500, Tom Prince
> wrote:
> > It is probably overkill for any one feature, but it does seem like
> > something useful to have. So maybe it would be worthwhile to create
> > for this one feature, even it it is overkill.
>
Formerly the xapian database object was deleted and closed in its
destructor once the object was garbage collected. Explicitly call
close() so that the database and the associated lock is released
immediately.
Signed-off-by: Justus Winter <4winter at informatik.uni-hamburg.de>
---
lib/database.cc
Pazz mentioned a problem wrt reopening a notmuch database immediately
after it has been closed. The problem can be reproduced with this test
case:
~~~ snip ~~~
import os
import notmuch
db_path = os.path.expanduser('~/Maildir')
for i in range(2):
with notmuch.Database(db_path, mode=notmuch.Da
---
test/search |2 ++
1 files changed, 2 insertions(+), 0 deletions(-)
diff --git a/test/search b/test/search
index 414be35..c55522b 100755
--- a/test/search
+++ b/test/search
@@ -130,6 +130,7 @@ output=$(notmuch search "bödý" | notmuch_search_sanitize)
test_expect_equal "$output" "thread:X
---
notmuch-count.c |8 +---
notmuch-search.c |8 +---
2 files changed, 2 insertions(+), 14 deletions(-)
diff --git a/notmuch-count.c b/notmuch-count.c
index 63459fb..f86cb40 100644
--- a/notmuch-count.c
+++ b/notmuch-count.c
@@ -35,9 +35,6 @@ notmuch_count_command (void *ctx, in
---
NEWS | 18 --
1 files changed, 0 insertions(+), 18 deletions(-)
diff --git a/NEWS b/NEWS
index b2bec04..5fa8043 100644
--- a/NEWS
+++ b/NEWS
@@ -11,24 +11,6 @@ Reply to sender
to all. The feature is available through the new command line option
--reply-to=(all|sender).
---
man/man1/notmuch-config.1 |8
1 files changed, 0 insertions(+), 8 deletions(-)
diff --git a/man/man1/notmuch-config.1 b/man/man1/notmuch-config.1
index 0260eb7..36e09f4 100644
--- a/man/man1/notmuch-config.1
+++ b/man/man1/notmuch-config.1
@@ -85,14 +85,6 @@ directory hierarchy.
This disables the addition of search_exclude_tags in notmuch-setup and
notmuch-config.
---
notmuch-config.c |3 +--
notmuch-setup.c | 19 +--
2 files changed, 2 insertions(+), 20 deletions(-)
diff --git a/notmuch-config.c b/notmuch-config.c
index e9b2750..61fda3e 100644
---
As requested by David (Bremner) on irc here is a patch series
disabling the search.exclude_tags feature as a temporary measure for
the 0.12 release.
There are two options:
The first is to disable the addition of the new search.exclude_tags
item to the config file and stop setup from asking for it
On Sun, 26 Feb 2012 16:59:53 -0500, Tom Prince
wrote:
> It is probably overkill for any one feature, but it does seem like
> something useful to have. So maybe it would be worthwhile to create
> for this one feature, even it it is overkill.
I can think of other features where some layer like thi
Hi!
The config syntax changed recently, when I switched from configparser to
configobj.
To clarify:
* the new config syntax is explained in the user docs at http://alot.rtfd.org.
These are auto-generated at each commit and correspond to the `testing`
branch,
which is where the bleeding edge
On Sat, 21 Jan 2012 09:09:58 -0400, David Bremner wrote:
> On Fri, 20 Jan 2012 09:44:06 +, Mark Walters gmail.com> wrote:
> > Define a keymap for attachment buttons to allow multiple actions.
> > Define 3 possible actions:
> > save attachment: exactly as currently,
> > view attachmen
The rest of the series still applies to master (bf28c60b9) but this patch
needed rebasing/restructuring to fit with the Austin's keep-state patch.
I attach the new patch below. Of course, if it is easier I can resend
the whole series.
Best wishes
Mark
>From 8324bc91e43d04e4c2813fa2a714766bcd0
Hi.
I had nottoomuch-addresses.sh working perfectly in emacs and I'm trying
to get it going in alot. Here's[1] what I've got so far. One things that
really confusing me is the brackets in the help file[2]. As soon as I
put double brackets alot can't read the account. Am I misunderstanding
somethi
On Tue, 28 Feb 2012 19:40:04 +0100, Pieter Praet wrote:
>
> Though I couldn't help but notice (it's a curse...) that patch #3
> seems to have gained an extra space in its commit message subject:
>
> Original (id:"1329684627-10708-4-git-send-email-pieter at praet.org"):
> emacs: add `notmuc
On Fri, 24 Feb 2012 08:36:22 +0100, Michal Sojka wrote:
> This fixes a bug that didn't allow to search for non-ASCII words such
> parts. The code here was copied from show_text_part_content(), because
> the show command already does the needed conversion when showing the
> message.
pushed both,
On Fri, 24 Feb 2012 01:33:15 +0100, Michal Sojka wrote:
> Emails that are encoded differently than as ASCII or UTF-8 are not
> indexed properly by notmuch. It is not possible to search for non-ASCII
> words within those messages.
pushed
d
On Tue, 28 Feb 2012 19:42:03 +0100, Pieter Praet wrote:
> * man/man1/notmuch-config.1
pushed
d
On Wed, 29 Feb 2012 10:36:57 -0500, Austin Clements wrote:
> What if the output of search (say, specifically the JSON format)
> included information on each message in the thread such as the
> 'message' production from devel/schemata minus the body field? Then
> the frontend would have loads of i
Quoth Justus Winter on Feb 29 at 10:19 am:
> Formerly the xapian database object was deleted and closed in its
> destructor once the object was garbage collected. Explicitly call
> close() so that the database and the associated lock is released
> immediately.
Interesting. Is this a bug in Xapian
Quoth Jesse Rosenthal on Feb 29 at 10:05 am:
> On Sun, 26 Feb 2012 16:59:53 -0500, Tom Prince
> wrote:
> > It is probably overkill for any one feature, but it does seem like
> > something useful to have. So maybe it would be worthwhile to create
> > for this one feature, even it it is overkill.
>
>
> Here is a News patch for this feature.
>
Also pushed. The commit message comes out slightly eccentric, but I
decided to leave it.
d
On Sun, 26 Feb 2012 16:59:53 -0500, Tom Prince wrote:
> It is probably overkill for any one feature, but it does seem like
> something useful to have. So maybe it would be worthwhile to create
> for this one feature, even it it is overkill.
I can think of other features where some layer like this
On Tue, 28 Feb 2012 19:40:04 +0100, Pieter Praet wrote:
>
> Though I couldn't help but notice (it's a curse...) that patch #3
> seems to have gained an extra space in its commit message subject:
>
> Original (id:"1329684627-10708-4-git-send-email-pie...@praet.org"):
> emacs: add `notmuch-s
On Fri, 24 Feb 2012 08:36:22 +0100, Michal Sojka wrote:
> This fixes a bug that didn't allow to search for non-ASCII words such
> parts. The code here was copied from show_text_part_content(), because
> the show command already does the needed conversion when showing the
> message.
pushed both,
On Fri, 24 Feb 2012 01:33:15 +0100, Michal Sojka wrote:
> Emails that are encoded differently than as ASCII or UTF-8 are not
> indexed properly by notmuch. It is not possible to search for non-ASCII
> words within those messages.
pushed
d
___
notmuch m
On Tue, 28 Feb 2012 19:42:03 +0100, Pieter Praet wrote:
> * man/man1/notmuch-config.1
pushed
d
___
notmuch mailing list
notmuch@notmuchmail.org
http://notmuchmail.org/mailman/listinfo/notmuch
>
> Here is a News patch for this feature.
>
Also pushed. The commit message comes out slightly eccentric, but I
decided to leave it.
d
___
notmuch mailing list
notmuch@notmuchmail.org
http://notmuchmail.org/mailman/listinfo/notmuch
On Sat, 21 Jan 2012 09:09:58 -0400, David Bremner wrote:
> On Fri, 20 Jan 2012 09:44:06 +, Mark Walters
> wrote:
> > Define a keymap for attachment buttons to allow multiple actions.
> > Define 3 possible actions:
> > save attachment: exactly as currently,
> > view attachment: uses
Formerly the xapian database object was deleted and closed in its
destructor once the object was garbage collected. Explicitly call
close() so that the database and the associated lock is released
immediately.
Signed-off-by: Justus Winter <4win...@informatik.uni-hamburg.de>
---
lib/database.cc |
Pazz mentioned a problem wrt reopening a notmuch database immediately
after it has been closed. The problem can be reproduced with this test
case:
~~~ snip ~~~
import os
import notmuch
db_path = os.path.expanduser('~/Maildir')
for i in range(2):
with notmuch.Database(db_path, mode=notmuch.Da
The rest of the series still applies to master (bf28c60b9) but this patch
needed rebasing/restructuring to fit with the Austin's keep-state patch.
I attach the new patch below. Of course, if it is easier I can resend
the whole series.
Best wishes
Mark
>From 8324bc91e43d04e4c2813fa2a714766bcd0
53 matches
Mail list logo
