On Wed, 17 Aug 2011 19:31:36 -0700, Alex Botero-Lowry wrote:
> p.s. I also ran into an issue with the notmuch python bindings where I had
> to wrap every c_void_p in POINTER() or it would segfault for any method that
> tried to use a pointer. Also the sed command that tries to build notmuch.sym
>
On Wed, 17 Aug 2011 19:31:36 -0700, Alex Botero-Lowry
alex.boterolo...@gmail.com wrote:
p.s. I also ran into an issue with the notmuch python bindings where I had
to wrap every c_void_p in POINTER() or it would segfault for any method that
tried to use a pointer. Also the sed command that
On Wed, 17 Aug 2011 19:31:36 -0700, Alex Botero-Lowry wrote:
> p.s. I also ran into an issue with the notmuch python bindings where I had
> to wrap every c_void_p in POINTER() or it would segfault for any method that
> tried to use a pointer. Also the sed command that tries to build notmuch.sym
>
On Wed, 17 Aug 2011 19:31:36 -0700, Alex Botero-Lowry
alex.boterolo...@gmail.com wrote:
p.s. I also ran into an issue with the notmuch python bindings where I had
to wrap every c_void_p in POINTER() or it would segfault for any method that
tried to use a pointer. Also the sed command that
I finally got around to working on it and over the last two days have gotten
two-way gmail syncing with labels working.
The list of caveats is much longer than the list of details:
1) only tested with 100 messages, which is hard coded
2) doesn't update UIDs of messages on disk, though it mostly
I finally got around to working on it and over the last two days have gotten
two-way gmail syncing with labels working.
The list of caveats is much longer than the list of details:
1) only tested with 100 messages, which is hard coded
2) doesn't update UIDs of messages on disk, though it mostly
