On 2015-10-02 21:21, David Bremner wrote:
>>> The problem is a References header that is too long/not wrapped.
>>>
>>
>> Hi Allan;
>>
>> Thanks for the report. I can see how notmuch-reply would generate a
>> long references header in that situation. We rely on message-mode
the idea is that you can run
% notmuch search 'subject:rx:'
or
% notmuch search subject:"your usual phrase search"
This should also work with bindings.
---
Here is Austin's "hack", crammed into the field processor framework.
I seem to have broken one of the existing subject search tests with
Quoth Gaute Hope on Jun 06 at 8:08 pm:
> Austin Clements writes on juni 6, 2016 21:20:
> >
> >The experiment was specifically for regexp matching subject, but it should
> >work for any header we store a literal copy of in the database.
>
> Does it work for terms in the body of the message?
No.
On Mon, Jun 6, 2016 at 1:29 PM, David Bremner wrote:
> Sebastian Fischmeister writes:
>
> >
> > I ran into this problem before as well. Storage is cheap. Notmuch could
> > index all emails with reversed text to get around some of this
> > problem. It
Austin Clements writes on juni 6, 2016 21:20:
The experiment was specifically for regexp matching subject, but it should
work for any header we store a literal copy of in the database.
Does it work for terms in the body of the message?
___
notmuch
Sebastian Fischmeister writes:
>
> I ran into this problem before as well. Storage is cheap. Notmuch could
> index all emails with reversed text to get around some of this
> problem. It doesn't solve the problem of *analysis*, but it's still an
> improvement.
It would
>> It is not possible to use wildcards at the beginning of a term.
>
> after the current explanation to emphasize this limitation (possibly
> blaming Xapian to avoid futile requests).
>
> I think it is something many would expect (and want). The current
> description feels more like an example,
Fix bug reported in id:20160606124522.g2y2eazhhrwjs...@flatcap.org
Although the C99 standard 6.10 is a little non-obvious on this point,
the docs for e.g. gcc are unambiguous. And indeed in practice with the
extra space, this code fails
int main(int argc, char **argv){
printf("%d\n",foo(1));
}
David Bremner writes:
> Fix bug reported in id:20160606124522.g2y2eazhhrwjs...@flatcap.org
>
> Although the C99 standard 6.10 is a little non-obvious on this point,
> the docs for e.g. gcc are unambiguous. And indeed in practice with the
> extra space, this code fails
>
> int
In the macro definition begins:
#define LIBNOTMUCH_CHECK_VERSION (major, minor, micro)
There shouldn't be a space before the (
This is from the current version in git.
Cheers,
Rich / FlatCap
___
notmuch mailing list
notmuch@notmuchmail.org
David Bremner writes on juni 6, 2016 14:42:
Gaute Hope writes:
Hi,
I have an email with the word 'reanalysis' in the subject line and the
email body. However, when I try to search for '*analysis' or 'analysis'
I do not get any matches, should not '*analysis' at least
Gaute Hope writes:
> Hi,
>
> I have an email with the word 'reanalysis' in the subject line and the
> email body. However, when I try to search for '*analysis' or 'analysis'
> I do not get any matches, should not '*analysis' at least match?
>
We talked about this on IRC
Hi,
I have an email with the word 'reanalysis' in the subject line and the
email body. However, when I try to search for '*analysis' or 'analysis'
I do not get any matches, should not '*analysis' at least match?
Regards, Gaute
___
notmuch mailing
On Mon, Jun 06 2016, David Bremner wrote:
> This was introduced with the libconfig changes, but not documented then.
> ---
>
> after some IRC discussion with Tomi, this rst is slightly less gross
LGTM.
Tomi
> doc/man1/notmuch-dump.rst | 10 +-
> 1 file changed, 9
14 matches
Mail list logo