Tomi Ollila writes:
> The notmuch cli program and emacs lisp versions may differ (especially
> in remote usage). It helps to resolve problems if we can determine
> the versions of notmuch cli and notmuch emacs mua separately.
>
> The build process now creates notmuch-version.el from template file
Excerpts from dm-list-email-notmuch's message of 2014-04-10 17:31:04 +0200:
> Gaute Hope writes:
>
> >> A better approach would be to add a new "modtime" xapian value that is
> >> updated whenever the tags or any other terms (such as XFDIRENTRY) are
> >> added to or deleted from a docid. If it's
Tomi Ollila writes:
> The notmuch cli program and emacs lisp versions may differ (especially
> in remote usage). It helps to resolve problems if we can determine
> the versions of notmuch cli and notmuch emacs mua separately.
>
> The build process now creates notmuch-version.el from template file
Excerpts from David Mazieres's message of 2014-04-06 22:19:19 +0200:
> Gaute Hope writes:
>
> > When one of the source files for a message is changed on disk, renamed,
> > deleted or a new source file is added. A configurable changed tag is
> > is added. The tag can be configured under the option
I'm thrilled by using notmuch to manage my mail. Low-latency search is
very important to me. But I use computers in a couple of
places---several of which are laptops. Has anyone stories to share of
successful multi-computer notmuch sync, for a corpus of a
quarter-million messages or so?
I've
Excerpts from dm-list-email-notmuch's message of 2014-04-10 17:31:04 +0200:
> Gaute Hope writes:
>
> >> A better approach would be to add a new "modtime" xapian value that is
> >> updated whenever the tags or any other terms (such as XFDIRENTRY) are
> >> added to or deleted from a docid. If it's
On Sat, 05 Apr 2014, David Bremner wrote:
> Supercedes
>
> id:1396554083-3892-2-git-send-email-david at tethera.net
>
> - adds new analogues of strerror
> - util_error_string
> - gz_error_string
LGTM other than the two nits I pointed out. I'd be happy to have the
fixes for those simply am
On Sat, 05 Apr 2014, David Bremner wrote:
> All we do here is calculate the backup filename, and call the existing
> dump routine.
>
> Also take the opportity to add a message about being safe to
opportunity
> interrupt.
> ---
> notmuch-new.c| 29 -
> test/T5
On Sat, 05 Apr 2014, David Bremner wrote:
> We rely completely on zlib to do the right thing in detecting gzipped
> input. Since our dump format is chosen to be 7 bit ascii, this should
> be fine.
> ---
> doc/man1/notmuch-restore.rst | 8
> notmuch-restore.c| 93
> +
Gaute Hope writes:
>> A better approach would be to add a new "modtime" xapian value that is
>> updated whenever the tags or any other terms (such as XFDIRENTRY) are
>> added to or deleted from a docid. If it's a Xapian value, rather than a
>> term, then modtime will be queriable just like date,
Gaute Hope writes:
>> A better approach would be to add a new "modtime" xapian value that is
>> updated whenever the tags or any other terms (such as XFDIRENTRY) are
>> added to or deleted from a docid. If it's a Xapian value, rather than a
>> term, then modtime will be queriable just like date,
Excerpts from David Mazieres's message of 2014-04-06 22:19:19 +0200:
> Gaute Hope writes:
>
> > When one of the source files for a message is changed on disk, renamed,
> > deleted or a new source file is added. A configurable changed tag is
> > is added. The tag can be configured under the option
On Sat, 05 Apr 2014, David Bremner wrote:
> Supercedes
>
> id:1396554083-3892-2-git-send-email-da...@tethera.net
>
> - adds new analogues of strerror
> - util_error_string
> - gz_error_string
LGTM other than the two nits I pointed out. I'd be happy to have the
fixes for those simply amend
On Sat, 05 Apr 2014, David Bremner wrote:
> All we do here is calculate the backup filename, and call the existing
> dump routine.
>
> Also take the opportity to add a message about being safe to
opportunity
> interrupt.
> ---
> notmuch-new.c| 29 -
> test/T5
On Sat, 05 Apr 2014, David Bremner wrote:
> We rely completely on zlib to do the right thing in detecting gzipped
> input. Since our dump format is chosen to be 7 bit ascii, this should
> be fine.
> ---
> doc/man1/notmuch-restore.rst | 8
> notmuch-restore.c| 93
> +
15 matches
Mail list logo