My recent changes to the saved search format broke the alphabetically
sorted saved sort option. This makes it work again.
Also, since the saved-search list is no longer an alist change the
names in the sort function to avoid confusion.
---
Thanks to Jani for pointing out the bug.
Best wishes
Mar
If the user has unsorted or alphabetically sorted saved-searches these
should continue to work. If they have some custom lisp sort function
then it will need updating to work with the new saved-sort
format. Document this, and how the updating should be done.
Also roll in the fix for the markdown i
Update the documentation for notmuch-saved-search-sort-function to
match the new format and recommend the best way to access the fields
(which should minimize breakage if we need to change the format again
in the future).
---
This could be rolled into
id:1397292033-26502-1-git-send-email-markwalt
On Sat, 12 Apr 2014, Mark Walters wrote:
> My recent changes to the saved search format broke the alphabetically
> sorted saved sort option. This makes it work again.
>
> Also, since the saved-search list is no longer an alist change the
> names in the sort function to avoid confusion.
> ---
> Tha
David Bremner writes:
> Supercedes
>
> id:1396554083-3892-2-git-send-email-da...@tethera.net
>
> - adds new analogues of strerror
> - util_error_string
> - gz_error_string
>
pushed, amended as suggested by Austin and Tomi.
d
___
notmuch maili
This fixes out-of-tree build when generating emacs/notmuch-version.el.
---
emacs/Makefile.local | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/emacs/Makefile.local b/emacs/Makefile.local
index ca039e5..dcb4995 100644
--- a/emacs/Makefile.local
+++ b/emacs/Makefile.local
@@ -21
My recent changes to the saved search format broke the alphabetically
sorted saved sort option. This makes it work again.
Also update docs for saved-search sort defcustom to match the new
format.
Finally, since the saved-search list is no longer an alist change the
names in the sort function to a
This is v2 of the collection of patches in
id:1397292033-26502-1-git-send-email-markwalters1...@gmail.com
The series makes the alphabetically sorted saved searches options work
again, documents the new saved search sorting format, and fixes some
of the markdown problesm in the original NEWS patch.
If the user has unsorted or alphabetically sorted saved-searches these
should continue to work. If they have some custom lisp sort function
then it will need updating to work with the new saved-sort
format. Document this, and how the updating should be done.
Also roll in fixes for the markdown in
On Sat, Apr 12 2014, Mark Walters wrote:
> This is v2 of the collection of patches in
> id:1397292033-26502-1-git-send-email-markwalters1...@gmail.com
>
> The series makes the alphabetically sorted saved searches options work
> again, documents the new saved search sorting format, and fixes some
Nils Dagsson Moskopp writes:
>
> mjw1009 can reproduce if the from-query contains an "@" and thinks the
> problem may be "something deeper down in notmuch (actually probably in
> xapian)".
My own experiments contradict that (see attached patch for a test to
run). The exact address is about twice
dm-list-email-notm...@scs.stanford.edu writes:
>
> As far as updating the test suite, etc., it's almost certain that the
> core notmuch developers would be unsatisfied with whatever I've done,
> since the code base is very clean and has a very uniform style. So when
> I say I'd want some "indicat
As it is defined in CONFIGURE_CXXFLAGS.
---
configure | 1 +
1 file changed, 1 insertion(+)
diff --git a/configure b/configure
index b8a3ce7..f447581 100755
--- a/configure
+++ b/configure
@@ -908,6 +908,7 @@ WITH_ZSH = ${WITH_ZSH}
# Combined flags for compiling and linking against all of the
As far as I can figure out, if a git repository is non-bare, then it
should either have core.worktree set, or the parent directory should
be the worktree. Since the parent directory is usually the user's home
directory, we don't want that. Although unlikely to be typed by
mistake
% cd $HOME && ln
On Sat, Apr 12 2014, David Bremner wrote:
> As far as I can figure out, if a git repository is non-bare, then it
> should either have core.worktree set, or the parent directory should
> be the worktree. Since the parent directory is usually the user's home
> directory, we don't want that. Althoug
Tomi Ollila writes:
>
> Based on that info change looks reasonable. I edited my ~/.nmbug/config
> and changed bare = false -> bare = true and nothing borke so far.
>
> so +1 from me.
>
> Tomi
I forgot to mention that I ran that way for a week or so without
problems.
d
_
Jameson Graef Rollins writes:
> This is a tweak to patch "emacs: sign/encrypt replies to
> signed/encrypted messages" to only add mml crypto flags for replys
> when crypto processing has been activated.
>
The (merged) patch seems straightforward and seems to work. I'll
probably push it tomorrow
My recent changes to the saved search format broke the alphabetically
sorted saved sort option. This makes it work again.
Also, since the saved-search list is no longer an alist change the
names in the sort function to avoid confusion.
---
Thanks to Jani for pointing out the bug.
Best wishes
Mar
If the user has unsorted or alphabetically sorted saved-searches these
should continue to work. If they have some custom lisp sort function
then it will need updating to work with the new saved-sort
format. Document this, and how the updating should be done.
Also roll in the fix for the markdown i
Update the documentation for notmuch-saved-search-sort-function to
match the new format and recommend the best way to access the fields
(which should minimize breakage if we need to change the format again
in the future).
---
This could be rolled into id:1397292033-26502-1-git-send-email-markwalte
On Sat, 12 Apr 2014, Mark Walters wrote:
> My recent changes to the saved search format broke the alphabetically
> sorted saved sort option. This makes it work again.
>
> Also, since the saved-search list is no longer an alist change the
> names in the sort function to avoid confusion.
> ---
> Tha
David Bremner writes:
> Supercedes
>
> id:1396554083-3892-2-git-send-email-david at tethera.net
>
> - adds new analogues of strerror
> - util_error_string
> - gz_error_string
>
pushed, amended as suggested by Austin and Tomi.
d
This fixes out-of-tree build when generating emacs/notmuch-version.el.
---
emacs/Makefile.local | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/emacs/Makefile.local b/emacs/Makefile.local
index ca039e5..dcb4995 100644
--- a/emacs/Makefile.local
+++ b/emacs/Makefile.local
@@ -21
This is v2 of the collection of patches in
id:1397292033-26502-1-git-send-email-markwalters1009 at gmail.com
The series makes the alphabetically sorted saved searches options work
again, documents the new saved search sorting format, and fixes some
of the markdown problesm in the original NEWS pat
My recent changes to the saved search format broke the alphabetically
sorted saved sort option. This makes it work again.
Also update docs for saved-search sort defcustom to match the new
format.
Finally, since the saved-search list is no longer an alist change the
names in the sort function to a
If the user has unsorted or alphabetically sorted saved-searches these
should continue to work. If they have some custom lisp sort function
then it will need updating to work with the new saved-sort
format. Document this, and how the updating should be done.
Also roll in fixes for the markdown in
On Sat, Apr 12 2014, Mark Walters wrote:
> This is v2 of the collection of patches in
> id:1397292033-26502-1-git-send-email-markwalters1009 at gmail.com
>
> The series makes the alphabetically sorted saved searches options work
> again, documents the new saved search sorting format, and fixes so
on-text attachment was scrubbed...
Name: 0001-WIP-new-performance-test-for-notmuch-count.patch
Type: text/x-diff
Size: 1119 bytes
Desc: not available
URL:
<http://notmuchmail.org/pipermail/notmuch/attachments/20140412/c9883ac1/attachment.patch>
dm-list-email-notmuch at scs.stanford.edu writes:
>
> As far as updating the test suite, etc., it's almost certain that the
> core notmuch developers would be unsatisfied with whatever I've done,
> since the code base is very clean and has a very uniform style. So when
> I say I'd want some "indi
As it is defined in CONFIGURE_CXXFLAGS.
---
configure | 1 +
1 file changed, 1 insertion(+)
diff --git a/configure b/configure
index b8a3ce7..f447581 100755
--- a/configure
+++ b/configure
@@ -908,6 +908,7 @@ WITH_ZSH = ${WITH_ZSH}
# Combined flags for compiling and linking against all of the a
As far as I can figure out, if a git repository is non-bare, then it
should either have core.worktree set, or the parent directory should
be the worktree. Since the parent directory is usually the user's home
directory, we don't want that. Although unlikely to be typed by
mistake
% cd $HOME && ln
On Sat, Apr 12 2014, David Bremner wrote:
> As far as I can figure out, if a git repository is non-bare, then it
> should either have core.worktree set, or the parent directory should
> be the worktree. Since the parent directory is usually the user's home
> directory, we don't want that. Althoug
Tomi Ollila writes:
>
> Based on that info change looks reasonable. I edited my ~/.nmbug/config
> and changed bare = false -> bare = true and nothing borke so far.
>
> so +1 from me.
>
> Tomi
I forgot to mention that I ran that way for a week or so without
problems.
d
Jameson Graef Rollins writes:
> This is a tweak to patch "emacs: sign/encrypt replies to
> signed/encrypted messages" to only add mml crypto flags for replys
> when crypto processing has been activated.
>
The (merged) patch seems straightforward and seems to work. I'll
probably push it tomorrow
34 matches
Mail list logo
