Use the new JSON reply format to create replies in emacs. Quote HTML
parts nicely by using mm-display-part to turn them into displayable
text, then quoting them with message-cite-original. This is very
useful for users who regularly receive HTML-only email.
Use message-mode's message-cite-original
Add tests for creating nice replies to multipart messages, including
those with HTML parts. These tests are expected to fail for now.
---
test/emacs | 97
1 files changed, 97 insertions(+), 0 deletions(-)
diff --git a/test/emacs b/tes
Move a few functions related to handling multipart/alternative parts
into notmuch-lib.el, so they can be used by future reply code.
---
emacs/notmuch-lib.el | 33 +
emacs/notmuch-show.el | 24 ++--
2 files changed, 35 insertions(+), 22 delet
---
man/man1/notmuch-reply.1 |5 +
1 files changed, 5 insertions(+), 0 deletions(-)
diff --git a/man/man1/notmuch-reply.1 b/man/man1/notmuch-reply.1
index 5160ece..307abee 100644
--- a/man/man1/notmuch-reply.1
+++ b/man/man1/notmuch-reply.1
@@ -43,6 +43,11 @@ include
.BR default
Include
---
devel/schemata | 27 +--
1 files changed, 25 insertions(+), 2 deletions(-)
diff --git a/devel/schemata b/devel/schemata
index d90d4c6..ee8cfc0 100644
--- a/devel/schemata
+++ b/devel/schemata
@@ -74,8 +74,9 @@ part = {
content?: string# pre-fetched bod
This new JSON format for replies includes headers generated for a
reply message as well as the headers of the original message. Using
this data, a client can intelligently create a reply. For example, the
emacs client will be able to create replies with quoted HTML parts by
parsing the HTML parts.
---
devel/TODO |5 +
1 files changed, 5 insertions(+), 0 deletions(-)
diff --git a/devel/TODO b/devel/TODO
index 4dda6f4..4ad1ee5 100644
--- a/devel/TODO
+++ b/devel/TODO
@@ -141,6 +141,11 @@ Simplify notmuch-reply to simply print the headers (we
have the
original values) rather than ca
As the semantics of replying to multiple messages have not yet been
defined well, make notmuch reply require that the search given returns
only a single message.
---
notmuch-reply.c | 36 +++-
1 files changed, 19 insertions(+), 17 deletions(-)
diff --git a/notmuc
Factor out the creation of a reply message based on an original
message so it can be shared by different reply formats.
---
notmuch-reply.c | 101 +++---
1 files changed, 58 insertions(+), 43 deletions(-)
diff --git a/notmuch-reply.c b/notmuch-repl
---
test/multipart | 52
1 files changed, 52 insertions(+), 0 deletions(-)
diff --git a/test/multipart b/test/multipart
index a3036b4..f102294 100755
--- a/test/multipart
+++ b/test/multipart
@@ -589,6 +589,58 @@ Non-text part: text/html
EOF
Hi all,
This is an updated version of my previous series [1], primarily addressing
the concerns from Austin's review. The big changes are:
* Documentation: add a TODO regarding reply to multiple messages and the
JSON reply format to schemata.
* Emacs: using plists instead of alists in JSON par
Hi Austin,
A couple of quick notes below, just before I send the new version:
On Fri, Feb 17, 2012 at 13:00, Austin Clements wrote:
> One of the biggest wins of using consistent JSON parsing settings is
> that this can be replaced with notmuch-show-mm-display-part-inline,
> which, as far as I ca
Use the new JSON reply format to create replies in emacs. Quote HTML
parts nicely by using mm-display-part to turn them into displayable
text, then quoting them with message-cite-original. This is very
useful for users who regularly receive HTML-only email.
Use message-mode's message-cite-original
---
devel/TODO |5 +
1 files changed, 5 insertions(+), 0 deletions(-)
diff --git a/devel/TODO b/devel/TODO
index 4dda6f4..4ad1ee5 100644
--- a/devel/TODO
+++ b/devel/TODO
@@ -141,6 +141,11 @@ Simplify notmuch-reply to simply print the headers (we
have the
original values) rather than ca
Move a few functions related to handling multipart/alternative parts
into notmuch-lib.el, so they can be used by future reply code.
---
emacs/notmuch-lib.el | 33 +
emacs/notmuch-show.el | 24 ++--
2 files changed, 35 insertions(+), 22 delet
Hi all,
This is an updated version of my previous series [1], primarily addressing
the concerns from Austin's review. The big changes are:
* Documentation: add a TODO regarding reply to multiple messages and the
JSON reply format to schemata.
* Emacs: using plists instead of alists in JSON par
---
man/man1/notmuch-reply.1 |5 +
1 files changed, 5 insertions(+), 0 deletions(-)
diff --git a/man/man1/notmuch-reply.1 b/man/man1/notmuch-reply.1
index 5160ece..307abee 100644
--- a/man/man1/notmuch-reply.1
+++ b/man/man1/notmuch-reply.1
@@ -43,6 +43,11 @@ include
.BR default
Include
---
test/multipart | 52
1 files changed, 52 insertions(+), 0 deletions(-)
diff --git a/test/multipart b/test/multipart
index a3036b4..f102294 100755
--- a/test/multipart
+++ b/test/multipart
@@ -589,6 +589,58 @@ Non-text part: text/html
EOF
---
devel/schemata | 27 +--
1 files changed, 25 insertions(+), 2 deletions(-)
diff --git a/devel/schemata b/devel/schemata
index d90d4c6..ee8cfc0 100644
--- a/devel/schemata
+++ b/devel/schemata
@@ -74,8 +74,9 @@ part = {
content?: string# pre-fetched bod
Add tests for creating nice replies to multipart messages, including
those with HTML parts. These tests are expected to fail for now.
---
test/emacs | 97
1 files changed, 97 insertions(+), 0 deletions(-)
diff --git a/test/emacs b/tes
This new JSON format for replies includes headers generated for a
reply message as well as the headers of the original message. Using
this data, a client can intelligently create a reply. For example, the
emacs client will be able to create replies with quoted HTML parts by
parsing the HTML parts.
Factor out the creation of a reply message based on an original
message so it can be shared by different reply formats.
---
notmuch-reply.c | 101 +++---
1 files changed, 58 insertions(+), 43 deletions(-)
diff --git a/notmuch-reply.c b/notmuch-repl
As the semantics of replying to multiple messages have not yet been
defined well, make notmuch reply require that the search given returns
only a single message.
---
notmuch-reply.c | 36 +++-
1 files changed, 19 insertions(+), 17 deletions(-)
diff --git a/notmuc
Hi Austin,
A couple of quick notes below, just before I send the new version:
On Fri, Feb 17, 2012 at 13:00, Austin Clements wrote:
> One of the biggest wins of using consistent JSON parsing settings is
> that this can be replaced with notmuch-show-mm-display-part-inline,
> which, as far as I ca
/notmuchmail.org/pipermail/notmuch/attachments/20120221/dfc5309c/attachment.pgp>
gmime-2.6 had a bug [1] which made it impossible to tell why a signature
verification failed when the signer key was unavailable (empty "sigstatus" field
in the JSON output). Since 00b5623d the corresponding test is marked as broken
when using gmime-2.6 (2.4 is fine).
This bug has been fixed in gm
On Tue, 21 Feb 2012 17:05:43 +0100, Thomas Jost
wrote:
> gmime 2.6 had a bug [1] which made it impossible to tell why a signature
> verification failed when the signer key was unavailable (empty "sigstatus"
> field
> in the JSON output). Since 00b5623d the corresponding test is marked as broken
On Tue, 21 Feb 2012 10:42:30 -0500, Austin Clements wrote:
> Third time's the charm. This fixes show refresh to not mark anything
> read when keeping state while refreshing and makes it the default.
+1. LGTM. Works well.
Tomi
On Tue, 21 Feb 2012 14:45:06 -0500, Daniel Kahn Gillmor
wrote:
> On 02/21/2012 11:49 AM, Tomi Ollila wrote:
> > I'm in favor of gmime >= 2.6.5 requirement.
>
> I tend to agree with Tomi here. I'm going to work on getting gmime
> 2.6.5 into debian later today.
gmime 2.6.6 is now in debian unsta
On Wed, Feb 15, 2012 at 10:14, Tomi Ollila wrote:
> On Wed, 15 Feb 2012 09:23:31 -0700, Adam Wolfe Gordon
> wrote:
> notmuch count is fast
> notmuch count --output=threads ?is slower
>
> I was thinking why not show both? but as threads
> count is slow there could be customization variable
> for
gmime 2.6 had a bug [1] which made it impossible to tell why a signature
verification failed when the signer key was unavailable (empty "sigstatus" field
in the JSON output). Since 00b5623d the corresponding test is marked as broken
when using gmime 2.6 (2.4 is fine).
The bug has been fixed in gmi
On Tue, 21 Feb 2012 09:15:09 -, Justus Winter <4winter at
informatik.uni-hamburg.de> wrote:
> I do get the feeling that it is perceived as desirable not to require
> any kind of notmuch bindings (David once said something similar about
> nmbug).
I think nmbug is a different case from an opti
On Wed, Feb 15, 2012 at 10:14, Tomi Ollila wrote:
> On Wed, 15 Feb 2012 09:23:31 -0700, Adam Wolfe Gordon
> wrote:
> notmuch count is fast
> notmuch count --output=threads is slower
>
> I was thinking why not show both? but as threads
> count is slow there could be customization variable
> for
Hi all,
Those of you with long enough backlog on the list to remember my rant
(id:20110626202733.GA26837 at brick)
can guess my opion on this matter but just to be sure..
I am not much of an expert on libnotmuch internals but am using the python
bindings extensively.
It feels super-strange usin
face though. (And
hence notmuch lends itself well to being used in shell scripts).
Cheers,
Daniel
-- next part --
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 835 bytes
Desc: not available
URL:
<http://notmuchmail.org/pipermail/notmuch/attachments/20120221/70f77db7/attachment.pgp>
On 02/21/2012 11:49 AM, Tomi Ollila wrote:
> I'm in favor of gmime >= 2.6.5 requirement.
I tend to agree with Tomi here. I'm going to work on getting gmime
2.6.5 into debian later today.
--dkg
On Tue, 21 Feb 2012 09:15:09 -, Justus Winter <4winter at
informatik.uni-hamburg.de> wrote:
> Quoting Daniel Schoepe (2012-02-17 02:28:52) [emphasis mine]:
> >Just for completeness: I'm using the nice nottoomuch-addresses.pl script
> >[1] by Tomi Ollila *which doesn't require any bindings* and
On Tue, 21 Feb 2012 09:15:09 -, Justus Winter
<4win...@informatik.uni-hamburg.de> wrote:
> I do get the feeling that it is perceived as desirable not to require
> any kind of notmuch bindings (David once said something similar about
> nmbug).
I think nmbug is a different case from an optiona
On 02/21/2012 11:49 AM, Tomi Ollila wrote:
> I'm in favor of gmime >= 2.6.5 requirement.
I tend to agree with Tomi here. I'm going to work on getting gmime
2.6.5 into debian later today.
--dkg
___
notmuch mailing list
notmuch@notmuchmail.org
ht
gmime-2.6 had a bug [1] which made it impossible to tell why a signature
verification failed when the signer key was unavailable (empty "sigstatus" field
in the JSON output). Since 00b5623d the corresponding test is marked as broken
when using gmime-2.6 (2.4 is fine).
This bug has been fixed in gm
On Tue, 21 Feb 2012 14:53:06 +0100, Daniel Schoepe
wrote:
> On Tue, 21 Feb 2012 09:15:09 -, Justus Winter <4winter at
> informatik.uni-hamburg.de> wrote:
> The reason I mentioned nottoomuch-addresses at all, is that completion
> itself is _a lot_ faster (at least for me), compared to
> addrl
Quoth Justus Winter on Feb 21 at 1:29 am:
> Hi fellow notmuchrs,
>
> while going through the python bindings I recently came across the
> following note in the documentation for the Database.get_directory
> function [0]:
>
> ~~~ snip ~~~
> Warning
>
> This call needs a writable database in Data
---
NEWS |5 +
1 files changed, 5 insertions(+), 0 deletions(-)
diff --git a/NEWS b/NEWS
index e9abb86..75fa2f4 100644
--- a/NEWS
+++ b/NEWS
@@ -63,6 +63,11 @@ More flexible and consistent tagging operations
(notmuch-show-tag-message "-unread")
+Refreshing the show view ('=' by def
Consensus seems to be that people prefer that refreshing show buffers
retains state by default, rather than resetting it by default. This
turns out to be the case in the code, as well. In fact, there's even
a test for this that's been marked broken for several months, which
this patch finally get
If we retain state while refreshing a show buffer, it should not mark
any messages read since it's not a navigation operation (it especially
shouldn't mark the first message matching the query read, which is
what it did previously). If the user or caller requests that refresh
reset the state of th
Third time's the charm. This fixes show refresh to not mark anything
read when keeping state while refreshing and makes it the default.
On Tue, 21 Feb 2012, Mark Walters wrote:
> On Sun, 19 Feb 2012 08:33:00 +0100, Michal Sojka
> wrote:
> > On Sun, 19 Feb 2012, Jani Nikula wrote:
> > > On Feb 19, 2012 12:44 AM, "Michal Sojka" wrote:
> > > >
> > > > After recent rework of a/A/x/X key bindings, the important paragraph in
> > > > d
On Mon, Feb 20, 2012 at 22:59, Austin Clements wrote:
> I've been thinking about this more. ?message-mode's default citation
> line is really unfortunate and quite possibly insane ("writes" isn't
> even the right tense and what's up with that extra line break?). ?The
> option to change this is als
Quoting Daniel Schoepe (2012-02-17 02:28:52) [emphasis mine]:
>Just for completeness: I'm using the nice nottoomuch-addresses.pl script
>[1] by Tomi Ollila *which doesn't require any bindings* and is incredibly
>fast (after generating an initial address database).
I don't get it. The perl script i
On Mon, Feb 20, 2012 at 22:59, Austin Clements wrote:
> I've been thinking about this more. message-mode's default citation
> line is really unfortunate and quite possibly insane ("writes" isn't
> even the right tense and what's up with that extra line break?). The
> option to change this is als
On Tue, 21 Feb 2012 17:05:43 +0100, Thomas Jost wrote:
> gmime 2.6 had a bug [1] which made it impossible to tell why a signature
> verification failed when the signer key was unavailable (empty "sigstatus"
> field
> in the JSON output). Since 00b5623d the corresponding test is marked as broken
>
On Sun, 19 Feb 2012 08:33:00 +0100, Michal Sojka wrote:
> On Sun, 19 Feb 2012, Jani Nikula wrote:
> > On Feb 19, 2012 12:44 AM, "Michal Sojka" wrote:
> > >
> > > After recent rework of a/A/x/X key bindings, the important paragraph in
> > > documentation of `notmuch-show-archive-thread' stayed hid
On Tue, 21 Feb 2012 10:42:30 -0500, Austin Clements wrote:
> Third time's the charm. This fixes show refresh to not mark anything
> read when keeping state while refreshing and makes it the default.
+1. LGTM. Works well.
Tomi
___
notmuch mailing list
On Tue, 21 Feb 2012 14:53:06 +0100, Daniel Schoepe wrote:
> On Tue, 21 Feb 2012 09:15:09 -, Justus Winter
> <4win...@informatik.uni-hamburg.de> wrote:
> The reason I mentioned nottoomuch-addresses at all, is that completion
> itself is _a lot_ faster (at least for me), compared to
> addrlooku
gmime 2.6 had a bug [1] which made it impossible to tell why a signature
verification failed when the signer key was unavailable (empty "sigstatus" field
in the JSON output). Since 00b5623d the corresponding test is marked as broken
when using gmime 2.6 (2.4 is fine).
The bug has been fixed in gmi
Quoth Justus Winter on Feb 21 at 1:29 am:
> Hi fellow notmuchrs,
>
> while going through the python bindings I recently came across the
> following note in the documentation for the Database.get_directory
> function [0]:
>
> ~~~ snip ~~~
> Warning
>
> This call needs a writable database in Data
On Thu, 9 Feb 2012 14:46:03 +, Jani Nikula wrote:
> Replace text/x-vcalendar with text/calendar, while maintaining support
> and backwards compatibility for text/x-vcalendar.
David (B, not E), while 1/2 needs work, this 2/2 is independent and IMHO
could go in.
BR,
Jani.
>
> Code by David
On Thu, 9 Feb 2012 14:46:02 +, Jani Nikula wrote:
> Make notmuch-show-all-multipart/alternative-parts accept a list of
> regexps to match the part types to determine which parts to show in
> addition to the preferred types. This allows the user to force display
> some alternative part types w
Consensus seems to be that people prefer that refreshing show buffers
retains state by default, rather than resetting it by default. This
turns out to be the case in the code, as well. In fact, there's even
a test for this that's been marked broken for several months, which
this patch finally get
---
NEWS |5 +
1 files changed, 5 insertions(+), 0 deletions(-)
diff --git a/NEWS b/NEWS
index e9abb86..75fa2f4 100644
--- a/NEWS
+++ b/NEWS
@@ -63,6 +63,11 @@ More flexible and consistent tagging operations
(notmuch-show-tag-message "-unread")
+Refreshing the show view ('=' by d
If we retain state while refreshing a show buffer, it should not mark
any messages read since it's not a navigation operation (it especially
shouldn't mark the first message matching the query read, which is
what it did previously). If the user or caller requests that refresh
reset the state of th
Third time's the charm. This fixes show refresh to not mark anything
read when keeping state while refreshing and makes it the default.
___
notmuch mailing list
notmuch@notmuchmail.org
http://notmuchmail.org/mailman/listinfo/notmuch
Hi all,
Those of you with long enough backlog on the list to remember my rant
(id:20110626202733.GA26837@brick)
can guess my opion on this matter but just to be sure..
I am not much of an expert on libnotmuch internals but am using the python
bindings extensively.
It feels super-strange using a
On Tue, 21 Feb 2012 09:15:09 -, Justus Winter
<4win...@informatik.uni-hamburg.de> wrote:
> Quoting Daniel Schoepe (2012-02-17 02:28:52) [emphasis mine]:
> >Just for completeness: I'm using the nice nottoomuch-addresses.pl script
> >[1] by Tomi Ollila *which doesn't require any bindings* and is
On Tue, 21 Feb 2012 09:15:09 -, Justus Winter
<4win...@informatik.uni-hamburg.de> wrote:
> Quoting Daniel Schoepe (2012-02-17 02:28:52) [emphasis mine]:
> >Just for completeness: I'm using the nice nottoomuch-addresses.pl script
> >[1] by Tomi Ollila *which doesn't require any bindings* and is
Quoting Daniel Schoepe (2012-02-17 02:28:52) [emphasis mine]:
>Just for completeness: I'm using the nice nottoomuch-addresses.pl script
>[1] by Tomi Ollila *which doesn't require any bindings* and is incredibly
>fast (after generating an initial address database).
I don't get it. The perl script i
On Tue, 21 Feb 2012, Mark Walters wrote:
> On Sun, 19 Feb 2012 08:33:00 +0100, Michal Sojka wrote:
> > On Sun, 19 Feb 2012, Jani Nikula wrote:
> > > On Feb 19, 2012 12:44 AM, "Michal Sojka" wrote:
> > > >
> > > > After recent rework of a/A/x/X key bindings, the important paragraph in
> > > > docu
Quoth Adam Wolfe Gordon on Feb 15 at 8:12 pm:
> Use the new JSON reply format to create replies in emacs. Quote HTML
> parts nicely by using mm-display-part to turn them into displayable
> text, then quoting them with message-cite-original. This is very
> useful for users who regularly receive HTM
On Sun, 19 Feb 2012 08:33:00 +0100, Michal Sojka wrote:
> On Sun, 19 Feb 2012, Jani Nikula wrote:
> > On Feb 19, 2012 12:44 AM, "Michal Sojka" wrote:
> > >
> > > After recent rework of a/A/x/X key bindings, the important paragraph in
> > > documentation of `notmuch-show-archive-thread' stayed hid
Hi fellow notmuchrs,
while going through the python bindings I recently came across the
following note in the documentation for the Database.get_directory
function [0]:
~~~ snip ~~~
Warning
This call needs a writable database in Database.MODE.READ_WRITE
mode. The underlying library will exit the
70 matches
Mail list logo
