the file?
At most (afaics) maybe you'd want to say something like:
[database]
path=/home/aj/Mail
path.old=git:///home/aj/OldMail.git
so that any filename starting with "old/" has the "old/" trimmed and
gets passed to the git backend, while the rest go to the default file
backend.
Cheers,
aj
--
Anthony Towns
the file?
At most (afaics) maybe you'd want to say something like:
[database]
path=/home/aj/Mail
path.old=git:///home/aj/OldMail.git
so that any filename starting with "old/" has the "old/" trimmed and
gets passed to the git backend, while the rest go to the
the return value if you want to
handle both use cases, without the compiler complaining about
const->non-const conversions in otherwise correct code in one case or
the other.
Cheers,
aj
--
Anthony Towns
be having it be a separate syntax would be good
-- then you could justify using information notmuch doesn't usually
have -- like file/path names, Received or Delivered-To headers, and so
on.
On the gripping hand, maybe "notmuch tag" should simply be fast enough
that running a bunch of them after "notmuch new" isn't an issue.
Cheers,
aj
--
Anthony Towns
the return value if you want to
handle both use cases, without the compiler complaining about
const->non-const conversions in otherwise correct code in one case or
the other.
Cheers,
aj
--
Anthony Towns
___
notmuch mailing list
notmuch@notmuchm
having it be a separate syntax would be good
-- then you could justify using information notmuch doesn't usually
have -- like file/path names, Received or Delivered-To headers, and so
on.
On the gripping hand, maybe "notmuch tag" should simply be fast enough
that runni
Hi *,
The attached patch makes "notmuch new --new-tags=unread,new" set the
"unread" and "new" tags on any new mail it finds rather than "unread"
and "inbox". Or whatever other tags you happen to specify.
Signed-off-by: Anthony Towns
-
Hi *,
The attached patch makes "notmuch new --new-tags=unread,new" set the
"unread" and "new" tags on any new mail it finds rather than "unread"
and "inbox". Or whatever other tags you happen to specify.
Signed-off-by: Anthony Towns
-
this one respect? [0]
$ notmuch count
96632
$ notmuch search
Error: notmuch search requires at least one search term.
...seems pretty logical behaviour to me?
Cheers,
aj
[0] Not much, afaics! [1]
[1] Man, what are the chances that will ever get old? [0]
--
Anthony Towns
any messages in the above new threads will automagically match on
# threadtag:merged or threadtag:postponed. Thus:
notmuch search threadtag:merged 123456..123789
That's abusing subthreads as a poor man's set. Not really convinced
that's a good idea, but what the hey... Something to think about
maybe.
Cheers,
aj
--
Anthony Towns
iour was necessary in order to do duplicate checking in a
sane way)
But anyway, that would let you do:
find Mail/.Drafts/ -type f | notmuch new --initial-tags=draft --file-list
notmuch new
to get drafts correctly tagged.
(I don't have the patches handy at the moment; but can certainly dig
them up if there's interest)
Cheers,
aj
--
Anthony Towns
this one respect? [0]
$ notmuch count
96632
$ notmuch search
Error: notmuch search requires at least one search term.
...seems pretty logical behaviour to me?
Cheers,
aj
[0] Not much, afaics! [1]
[1] Man, what are the chances that will ever get old? [0]
--
Anthony Towns
__
any messages in the above new threads will automagically match on
# threadtag:merged or threadtag:postponed. Thus:
notmuch search threadtag:merged 123456..123789
That's abusing subthreads as a poor man's set. Not really convinced
that's a good idea, but what the hey... So
him at least once)
That seems to be a different id to
http://patchwork.notmuchmail.org/patch/445/ but "me too" on that,
fwiw. (Haven't had data loss, did have confusing behaviour that I
attribute to this, and the logic for the patch seems sound to me)
Cheers,
aj
--
Anthony Towns
iour was necessary in order to do duplicate checking in a
sane way)
But anyway, that would let you do:
find Mail/.Drafts/ -type f | notmuch new --initial-tags=draft --file-list
notmuch new
to get drafts correctly tagged.
(I don't have the patches handy at the momen
t least once)
That seems to be a different id to
http://patchwork.notmuchmail.org/patch/445/ but "me too" on that,
fwiw. (Haven't had data loss, did have confusing behaviour that I
attribute to this, and the logic for the patch seems sound to me)
Ch
ze_t len)
char *
json_quote_str(const void *ctx, const char *str)
{
+if (str == NULL)
+ str = "";
+
return (json_quote_chararray (ctx, str, strlen (str)));
}
--
Anthony Towns
ze_t len)
char *
json_quote_str(const void *ctx, const char *str)
{
+if (str == NULL)
+ str = "";
+
return (json_quote_chararray (ctx, str, strlen (str)));
}
--
Anthony Towns
___
notmuch mailing list
notmuch@notmuchmail.org
http://notmuchmail.org/mailman/listinfo/notmuch
ght tags -- this coule probably be implied in any
invocation of notmuch tag really...
Anyway, attached. It converts gmail's list: match to a notmuch to:
match, and just gives up on deliveredto: matches. But maybe someone
else finds it useful/interesting too :)
Cheers,
aj
[0] id:87r5o8s
tags -- this coule probably be implied in any
invocation of notmuch tag really...
Anyway, attached. It converts gmail's list: match to a notmuch to:
match, and just gives up on deliveredto: matches. But maybe someone
else finds it useful/interesting too :)
Cheers,
aj
[0] id:87r5o8stbj@yoom.
20 matches
Mail list logo