intel.com
-- next part --
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL:
<http://notmuchmail.org/pipermail/notmuch/attachments/20110128/0d36c49b/attachment.pgp>
On 2011-01-23, Michal Sojka wrote:
> Hi all,
>
> the following patch series brings into notmuch date/time parser stolen
> from GNU coreutils. It can be applied on top of custom query parser
> patches from Austin Clements.
>
> This is RFC and it not meant for merging.
Another source for date pars
On Fri, 28 Jan 2011 16:11:00 -0500, Jesse Rosenthal
wrote:
>
> Hmm... looks like a problem with ConfigParser. Maybe the default values
> aren't working well?
>
> Try setting up a ~/.notmuchprintrc:
>
> notmuch_command: "/usr/local/bin/notmuch"
> browser_command: "/usr/bin/firefox"
> plain_text
Looks like I managed to remove the line that deletes (and thus closes
and unlocks) the Xapian::Database object in a bout of overzealous code
removal. The consequence was exactly what you suspected; there was a
brief window after notmuch had exited before the database actually got
unlocked. Here's
Dear Jesse,
> Printing from notmuch is a bit of a pain. Muttprint doesn't really help
> much, because it can't handle multiparts well, doesn't know what to do
> with html, and will print out pages of base64 if you have
> attachments. And more often than not, what I need to print is an HTML
> emai
On 2011-01-23, Michal Sojka wrote:
> Hi all,
>
> the following patch series brings into notmuch date/time parser stolen
> from GNU coreutils. It can be applied on top of custom query parser
> patches from Austin Clements.
>
> This is RFC and it not meant for merging.
Another source for date pars
Looks like I managed to remove the line that deletes (and thus closes
and unlocks) the Xapian::Database object in a bout of overzealous code
removal. The consequence was exactly what you suspected; there was a
brief window after notmuch had exited before the database actually got
unlocked. Here's
Carl Worth writes:
> What do other build systems generally do when running configure from
> some other directory? Copy/link the Makefiles and then construct them
> carefully such that they can find all the source files?
I think the use of GNU make VPATH is fairly common. For example, I
believe
On Fri, 28 Jan 2011 16:11:00 -0500, Jesse Rosenthal
wrote:
> Hmm... looks like a problem with ConfigParser. Maybe the default values
> aren't working well?
Yep, that was the problem. It turns out it doesn't take True and False
as defaults -- needs strings ("yes", "no", "true", "false) or 1 or
0.
Hi Andreas,
On Fri, 28 Jan 2011 20:59:06 +, Andreas Amann wrote:
> Unfortunately I could not get it to work with python2.7:
>
> Traceback (most recent call last):
> File "/home/amann/local/bin/notmuchprint", line 284, in
> main(config)
> File "/home/amann/local/bin/notmuchprint", l
st for now.
-Carl
--
carl.d.worth at intel.com
-- next part --
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL:
<http://notmuchmail.org/pipermail/notmuch/attachments/20110128/fa1eb172/attachment.pgp>
On Fri, 28 Jan 2011 10:45:19 +0100, Thomas Schwinge
wrote:
> > It would definitely be nice to avoid the complexity inherent in having a
> > daemon, but how do you imagine "queue on a lock" to work? We don't have
> > anything like that in place now.
>
> I suppose what he means is trying to get the
Dear all,
Printing from notmuch is a bit of a pain. Muttprint doesn't really help
much, because it can't handle multiparts well, doesn't know what to do
with html, and will print out pages of base64 if you have
attachments. And more often than not, what I need to print is an HTML
email (a bus tick
Carl Worth writes:
> What do other build systems generally do when running configure from
> some other directory? Copy/link the Makefiles and then construct them
> carefully such that they can find all the source files?
I think the use of GNU make VPATH is fairly common. For example, I
believe
Hi Carl and Thomas,
On Sat, 29 Jan 2011 05:59:38 +1000 Carl Worth wrote:
> Yes, I believe this is related to the dot in the name. From my
> recollection a name with an address requires quoting. So the header
> that is currently formatted as:
>
> From: LWN.net Weekly Notification
>
> sho
On Fri, 28 Jan 2011 12:54:17 +1000, Carl Worth wrote:
> On Thu, 27 Jan 2011 10:51:42 -0500, Jesse Rosenthal
> wrote
> It sounds entirely useful for a large class of users. Is there any
> reason we shouldn't just host the script in the notmuch repository
> itself? Let me know if there's anything
as scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL:
<http://notmuchmail.org/pipermail/notmuch/attachments/20110128/5d7df2b8/attachment-0001.pgp>
xtend the
date back into the past and try to keep working through things.
-- next part --
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL:
<http://notmuchmail.org/pipermail/notmuch/attachments/20110128/6bf21b58/attachment-0001.pgp>
On Fri, 28 Jan 2011 16:11:00 -0500, Jesse Rosenthal wrote:
>
> Hmm... looks like a problem with ConfigParser. Maybe the default values
> aren't working well?
>
> Try setting up a ~/.notmuchprintrc:
>
> notmuch_command: "/usr/local/bin/notmuch"
> browser_command: "/usr/bin/firefox"
> plain_text_
On Tue, 11 Jan 2011 16:01:00 +0200, Felipe Contreras
wrote:
> I think this should be part of notmuch itself,
I'll be happy to see any proposed additions for this. (And to the extent
that some of this functionality exists in patches already proposed and
just waiting for me, then I'm already happy
On Wed, 12 Jan 2011 22:39:45 +, Mike Kelly wrote:
> For starters, if I'm simply trying to retrieve a single message, the
> interface is rather awkard. I seem to need to do something like:
>
> my $json = `notmuch show --format=json id:$message_id`;
> my $parsed_json = decode_json($json
On Wed, 12 Jan 2011 19:37:21 +0100, Christophe-Marie Duquesne
wrote:
> So I am wondering: what is the point of having a tool that is able to
> output json and ending in not using it? Is there a solution to make
> the json output more useable? One solution I've been thinking about
> would be to ad
> +if ! { : < configure; } 2> /dev/null; then
> +cat < +*** Error: You have to configure and build in the source directory.
> +
> +EOF
> +exit 1
> +fi
Rather than documenting a limitation here, why don't we do what people
actually want.
What do other build systems generally do when runnin
On Wed, 12 Jan 2011 15:50:24 -0500, Austin Clements wrote:
> Out of curiosity, has anyone considered using inotify to monitor maildirs
> for new mail to hand to notmuch? For systems supporting inotify (or
> equivalents), this would have the advantage of being compatible with any
> delivery mechan
On Wed, 8 Dec 2010 16:58:44 -0500, Austin Clements wrote:
> Now that this is in (and I have a temporary respite from TA duties),
> I'm going to finish up and send out my other ~1.7X improvement, just
> to get it out of my queue. Then I'll look at making a performance
> regression suite. Were you
On Wed, 8 Dec 2010 17:01:53 -0500, Austin Clements wrote:
> Remove the repeated "sizeof (doc_ids->bitmap[0])" that bothered cworth
> by instead defining macros to compute the word and bit offset of a
> given bit in the bitmap.
>
> Don't require the caller of _notmuch_doc_id_set_init to pass in a
On Tue, 11 Jan 2011 12:46:38 +0100, Thomas Schwinge
wrote:
> > What's the best way to advertise this to potential users?
>
> I recently put a description and link onto the notmuch web pages.
Great. Thanks for doing this.
> > Should we include a separate utils directory in the notmuch repositor
On Thu, 27 Jan 2011 03:31:49 -0700, Thomas Schwinge
wrote:
> These tests should pass -- but they currently don't.
Hi Thomas,
Thanks for sending these test cases. This is actually my favorite way to
receive bug reports. I really appreciate it!
> What we get from these emails, is an author named
On Thu, 13 Jan 2011 19:46:29 +0100, Christophe-Marie Duquesne
wrote:
> I've had a look to the python libnotmuch documentation. My problem
> with this API is that, unless I did not read it correctly, if I use
> one of its functions in a threaded fashion, I still have to wait for
> this function to
Actually, this is trivial to play with. Here's a stop-gap wrapper
script for people having trouble with Xapian locking,
#!/bin/bash
NOTMUCH_BIN="/path/to/notmuch"
MAIL_DIR="/path/to/mailroot"
(
case "$1" in
setup|help)
;;
search|show|count|reply|dump|search-tags|
On Fri, 28 Jan 2011 16:11:00 -0500, Jesse Rosenthal wrote:
> Hmm... looks like a problem with ConfigParser. Maybe the default values
> aren't working well?
Yep, that was the problem. It turns out it doesn't take True and False
as defaults -- needs strings ("yes", "no", "true", "false) or 1 or
0.
Hi Andreas,
On Fri, 28 Jan 2011 20:59:06 +, Andreas Amann wrote:
> Unfortunately I could not get it to work with python2.7:
>
> Traceback (most recent call last):
> File "/home/amann/local/bin/notmuchprint", line 284, in
> main(config)
> File "/home/amann/local/bin/notmuchprint", l
Dear Jesse,
> Printing from notmuch is a bit of a pain. Muttprint doesn't really help
> much, because it can't handle multiparts well, doesn't know what to do
> with html, and will print out pages of base64 if you have
> attachments. And more often than not, what I need to print is an HTML
> emai
not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL:
<http://notmuchmail.org/pipermail/notmuch/attachments/20110128/51898d9d/attachment.pgp>
Dear all,
Printing from notmuch is a bit of a pain. Muttprint doesn't really help
much, because it can't handle multiparts well, doesn't know what to do
with html, and will print out pages of base64 if you have
attachments. And more often than not, what I need to print is an HTML
email (a bus tick
On Fri, 28 Jan 2011 12:54:17 +1000, Carl Worth wrote:
> On Thu, 27 Jan 2011 10:51:42 -0500, Jesse Rosenthal wrote
> It sounds entirely useful for a large class of users. Is there any
> reason we shouldn't just host the script in the notmuch repository
> itself? Let me know if there's anything I
kends/flint_lock.cc,
which is hard-coded to the non-blocking F_SETLK instead of F_SETLKW), so
we'd either need a new Xapian option, or we would just have to wrap our own
flock/fcntl lock around things as you suggest.
-- next part --
An HTML attachment was scrubbed...
URL:
<http://notmuchmail.org/pipermail/notmuch/attachments/20110128/3f25e30c/attachment.html>
notmuch
operation block and queue up on the database lock, then have the client
update the display to "committed" when the asynchronous operation returns.
No weird database operations or transactional semantics and the client side
is fairly straightforward.
-- next part --
An HTML attachment was scrubbed...
URL:
<http://notmuchmail.org/pipermail/notmuch/attachments/20110128/c62788b6/attachment.html>
ned from
>
> git://rtime.felk.cvut.cz/notmuch.git custom-query-pasrser
>
> Thanks
> -Michal
> ___
> notmuch mailing list
> notmuch at notmuchmail.org
> http://notmuchmail.org/mailman/listinfo/notmuch
>
-- next part --
An HTML attachment was scrubbed...
URL:
<http://notmuchmail.org/pipermail/notmuch/attachments/20110128/97bda4b5/attachment.html>
Hi Austin,
when I switched to using your custom query parser I started experiencing
"Unable to get write lock" errors when I run my initial tagging script.
I thought that this was because I run the script while processing the
mail in Emacs, but today I realized that this happens even without Emacs
t very much into DBs, and neither too much into
concurrent systems, so if my ideas don't make sense, please feel free to
refer me to literature.
Gr??e,
Thomas
-- next part --
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: not available
URL:
<http://notmuchmail.org/pipermail/notmuch/attachments/20110128/a3d67691/attachment.pgp>
Actually, this is trivial to play with. Here's a stop-gap wrapper
script for people having trouble with Xapian locking,
#!/bin/bash
NOTMUCH_BIN="/path/to/notmuch"
MAIL_DIR="/path/to/mailroot"
(
case "$1" in
setup|help)
;;
search|show|count|reply|dump|search-tags|
ilable
Type: application/pgp-signature
Size: 197 bytes
Desc: not available
URL:
<http://notmuchmail.org/pipermail/notmuch/attachments/20110128/2378ba4f/attachment.pgp>
On Fri, Jan 28, 2011 at 10:36 AM, Mike Kelly wrote:
> On Fri, 28 Jan 2011 10:45:19 +0100, Thomas Schwinge
> wrote:
> > > It would definitely be nice to avoid the complexity inherent in having
> a
> > > daemon, but how do you imagine "queue on a lock" to work? We don't have
> > > anything like th
On Fri, Jan 28, 2011 at 4:45 AM, Thomas Schwinge wrote:
> On Fri, 28 Jan 2011 15:10:01 +1000, Carl Worth wrote:
> > On Thu, 27 Jan 2011 17:20:21 -0500, Austin Clements
> wrote:
> > > I'm looking into breaking notmuch new up into small transactions. It
> > > wouldn't be much a leap from there to
oo
late already. But then, it would have been a rather inconvenient time /
timezone anyways, being based in Germany. So, how has it been?
-- next part --
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: not available
URL:
<http://notmuchmail.org/pipermail/notmuch/attachments/20110128/a7d49d4e/attachment.pgp>
This should most definitely not happen. I'll look in to it.
On Fri, Jan 28, 2011 at 5:18 AM, Michal Sojka wrote:
> Hi Austin,
>
> when I switched to using your custom query parser I started experiencing
> "Unable to get write lock" errors when I run my initial tagging script.
> I thought that t
On Fri, 28 Jan 2011 10:45:19 +0100, Thomas Schwinge
wrote:
> > It would definitely be nice to avoid the complexity inherent in having a
> > daemon, but how do you imagine "queue on a lock" to work? We don't have
> > anything like that in place now.
>
> I suppose what he means is trying to get the
On Fri, 28 Jan 2011 08:45:35 +0100, Thomas Schwinge
wrote:
> Matches my thoughts :-) -- and as it occurs to me right now, doing it in
> one here document should be possible like this, if additional_headers is
> changed to have the newline *at the beginning* of the string:
...
> Date: ${templa
Hi Austin,
when I switched to using your custom query parser I started experiencing
"Unable to get write lock" errors when I run my initial tagging script.
I thought that this was because I run the script while processing the
mail in Emacs, but today I realized that this happens even without Emacs
Hallo!
On Fri, 28 Jan 2011 15:10:01 +1000, Carl Worth wrote:
> On Thu, 27 Jan 2011 17:20:21 -0500, Austin Clements wrote:
> > I'm looking into breaking notmuch new up into small transactions. It
> > wouldn't be much a leap from there to simply close and reopen the database
> > between transacti
On Thu, 27 Jan 2011 19:08:38 -0500, Austin Clements wrote:
> I added a "notmuch_database_remove_message_get" to the public API that's
> just like "notmuch_database_remove_message" except that it also returns a
> notmuch_message_t if other instances of the message still exist. It feels
> clunky t
52 matches
Mail list logo
