Tomi Ollila writes:
> On Sun, Oct 05 2014, David Bremner wrote:
>
>> It blows things up by a factor of six or so, so it's worth giving
>> people a heads up. It won't effect e.g. Debian, that already builds
>> with -g and then strips.
>
> Maybe SomeOne(™) could make a patch that strip(1)s at make
"W. Trevor King" writes:
> On Tue, Oct 07, 2014 at 08:30:34AM +0200, David Bremner wrote:
>> W. Trevor King writes:
>> > This is mostly culled from the commit message for 7f2cb3be (nmbug:
>> > Translate to Python, 2014-10-03). I realized while writing it
>> > that the 7f2cb3be commit message has
notmuch search --offset` simply skips the number of threads/messages.
This is not so fast if the offset is large.
98 for (i = 0;
99 notmuch_threads_valid (threads) && (limit < 0 || i <
offset + limit);
100 notmuch_threads_move_to_next (threads), i++)
101 {
102
Lets consider messages first.
As far as I get there is no straightforward
notmuch_messages_move_to_previous. One can usually implement such
behaviour with caching previous messages which is slightly inefficient
in memory consumption terms.
But we can sort messages either date asc or date desc.
S
On Tue, 07 Oct 2014, Sergei Shilovsky wrote:
> Lets consider messages first.
>
> As far as I get there is no straightforward
> notmuch_messages_move_to_previous. One can usually implement such
> behaviour with caching previous messages which is slightly inefficient
> in memory consumption terms.
>
Currently the thread is named based on either the oldest or newest
matching message (depending on the search order). If this message has
an empty subject, though, the thread will show up with an empty
subject in the search results. (See the thread starting with
`id:1412371140-21051-1-git-send-email
For more details, see the commit message for 7f2cb3be (nmbug:
Translate to Python, 2014-10-03). I realized while writing this that
the 7f2cb3be commit message has:
* 'nmbug log' now execs 'git log', as there's no need to keep the
Python process around once we've launched Git there.
But we
For more details, see the commit message for 7f2cb3be (nmbug:
Translate to Python, 2014-10-03). I realized while writing this that
the 7f2cb3be commit message has:
* 'nmbug log' now execs 'git log', as there's no need to keep the
Python process around once we've launched Git there.
But we
"W. Trevor King" writes:
> On Tue, Oct 07, 2014 at 08:30:34AM +0200, David Bremner wrote:
>> W. Trevor King writes:
>> > This is mostly culled from the commit message for 7f2cb3be (nmbug:
>> > Translate to Python, 2014-10-03). I realized while writing it
>> > that the 7f2cb3be commit message has
On Tue, Oct 07, 2014 at 08:30:34AM +0200, David Bremner wrote:
> W. Trevor King writes:
> > This is mostly culled from the commit message for 7f2cb3be (nmbug:
> > Translate to Python, 2014-10-03). I realized while writing it
> > that the 7f2cb3be commit message has:
>
> This seems a bit long for
ture.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: OpenPGP digital signature
URL:
<http://notmuchmail.org/pipermail/notmuch/attachments/20141007/a9d6b920/attachment.pgp>
Currently the thread is named based on either the oldest or newest
matching message (depending on the search order). If this message has
an empty subject, though, the thread will show up with an empty
subject in the search results. (See the thread starting with
`id:1412371140-21051-1-git-send-email
scrubbed...
Name: notmuch-cache.el
Type: application/emacs-lisp
Size: 3515 bytes
Desc: not available
URL:
<http://notmuchmail.org/pipermail/notmuch/attachments/20141007/3a7756a0/attachment-0001.bin>
mail.org/pipermail/notmuch/attachments/20141007/b422018a/attachment.obj>
Amadeusz ?o?nowski writes:
> Hi,
>
> With version 7.8 of gdb atomicity tests fail. With version 7.7.1 all
> tests pass.
>
This should be fixed in commit cbbda62
d
"W. Trevor King" writes:
> This is mostly culled from the commit message for 7f2cb3be (nmbug:
> Translate to Python, 2014-10-03). I realized while writing it that
> the 7f2cb3be commit message has:
This seems a bit long for a NEWS item, especially for a change that
impacts only a minority of cu
Hi David,
David Edmondson writes:
> ...here is a very simple filesystem based cache of MIME parts for
> notmuch. It's integrated using defadvice for now, but a cleaner
> approach is obviously possible.
Just to say that this is great, and very much appreciated. There are
some threads I avoided o
notmuch search --offset` simply skips the number of threads/messages.
This is not so fast if the offset is large.
98 for (i = 0;
99 notmuch_threads_valid (threads) && (limit < 0 || i <
offset + limit);
100 notmuch_threads_move_to_next (threads), i++)
101 {
102
Hi David,
David Edmondson writes:
> ...here is a very simple filesystem based cache of MIME parts for
> notmuch. It's integrated using defadvice for now, but a cleaner
> approach is obviously possible.
Just to say that this is great, and very much appreciated. There are
some threads I avoided o
On Tue, 07 Oct 2014, Sergei Shilovsky wrote:
> Lets consider messages first.
>
> As far as I get there is no straightforward
> notmuch_messages_move_to_previous. One can usually implement such
> behaviour with caching previous messages which is slightly inefficient
> in memory consumption terms.
>
Lets consider messages first.
As far as I get there is no straightforward
notmuch_messages_move_to_previous. One can usually implement such
behaviour with caching previous messages which is slightly inefficient
in memory consumption terms.
But we can sort messages either date asc or date desc.
S
On Tue, Oct 07 2014, David Edmondson wrote:
> I've been using remote-notmuch over a 3G connection quite a lot
> recently. Dragging down the same MIME part more than once is annoying,
> so here is a very simple filesystem based cache of MIME parts for
> notmuch. It's integrated using defadvice for n
I've been using remote-notmuch over a 3G connection quite a lot
recently. Dragging down the same MIME part more than once is annoying,
so here is a very simple filesystem based cache of MIME parts for
notmuch. It's integrated using defadvice for now, but a cleaner approach
is obviously possible.
N
23 matches
Mail list logo
