From: Dmitry Kurochkin <dmitry.kurochkin@gmail.com>
To: Adam Wolfe Gordon <awg@xvx.ca>, David Edmondson <dme@dme.org>
Cc: notmuch@notmuchmail.org
Subject: Re: [PATCH 4/4] emacs: Use the new JSON reply format.
Date: Thu, 12 Jan 2012 12:33:58 +0400 [thread overview]
Message-ID: <87k44xgw09.fsf@gmail.com> (raw)
In-Reply-To: <CAMoJFUt8F417wzSmiHDv2KHa9y5ARYh=xRHKEsWBXYXHfaN64A@mail.gmail.com>
Hi Adam.
On Mon, 9 Jan 2012 19:10:48 -0700, Adam Wolfe Gordon <awg@xvx.ca> wrote:
> Hi David,
>
> Thanks for the review. Most of the things you've suggested are easy
> changes, and I think obvious improvements, so I'll change them for the
> next version. A bit of discussion on the more involved things below:
>
> On Mon, Jan 9, 2012 at 01:50, David Edmondson <dme@dme.org> wrote:
> > On Sun, 8 Jan 2012 00:52:42 -0700, Adam Wolfe Gordon <awg+notmuch@xvx.ca> wrote:
> >> +(defun w3m-region (start end)) ;; From `w3m.el'.
> >> +(defun notmuch-mua-quote-part (part)
> >> + (with-temp-buffer
> >> + (insert part)
> >> + (message-mode)
> >> + (fill-region (point-min) (point-max))
> >> + (goto-char (point-min))
> >> + (perform-replace "^" "> " nil t nil)
> >> + (set-buffer-modified-p nil)
> >> + (buffer-substring (point-min) (point-max))))
> >
> > Couldn't all of this be done directly in the reply buffer?
>
> Indeed, it could, I just hadn't thought of it. I'll do this for the
> next version.
>
> > Using w3m means that you should `require' it. What happens when a user
> > doesn't have it? (Either the elisp or the command.)
>
> This was my initial thought, but when I looked at notmuch-show.el,
> which uses w3m features, I noticed that it doesn't have a require. To
> be clear, this patch requires w3m.el (not just the w3m binary), which
> I don't think anything else in notmuch does.
>
> In the previous version I had a customize variable specifying whether
> to quote HTML parts, which meant that if the user could set the
> customize variable to false and everything would work without w3m.el.
> I'd like not to introduce a new prerequisite, so if there's a way to
> make w3m.el optional that would be my preference. Can you provide
> some guidance on this?
>
I did not follow the rest of the discussion, so sorry if I missed
something obvious. But why can't we render HTML parts in replies the
same way we do in notmuch-show (using `mm-display-part')? That should
not introduce a w3m.el requirement, would use the same renderer as
configured for show and hence would produce consistent output in show
and reply.
Regards,
Dmitry
> --
> Adam Wolfe Gordon
> _______________________________________________
> notmuch mailing list
> notmuch@notmuchmail.org
> http://notmuchmail.org/mailman/listinfo/notmuch
next prev parent reply other threads:[~2012-01-12 8:34 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-08 7:52 [PATCH 0/4] Quoting HTML-only emails in replies redux Adam Wolfe Gordon
2012-01-08 7:52 ` [PATCH 1/4] test: Add broken test for the new JSON reply format Adam Wolfe Gordon
2012-01-08 7:52 ` [PATCH 2/4] reply: Add a " Adam Wolfe Gordon
2012-01-14 20:58 ` Jani Nikula
2012-01-08 7:52 ` [PATCH 3/4] man: Update notmuch-reply man page for JSON format Adam Wolfe Gordon
2012-01-08 7:52 ` [PATCH 4/4] emacs: Use the new JSON reply format Adam Wolfe Gordon
2012-01-09 1:27 ` Aaron Ecay
2012-01-10 1:59 ` Adam Wolfe Gordon
2012-01-09 8:50 ` David Edmondson
2012-01-10 2:10 ` Adam Wolfe Gordon
2012-01-10 7:25 ` David Edmondson
2012-01-12 8:33 ` Dmitry Kurochkin [this message]
2012-01-12 12:07 ` David Edmondson
2012-01-12 13:36 ` Tomi Ollila
2012-01-12 13:43 ` David Edmondson
2012-01-15 21:19 ` Adam Wolfe Gordon
2012-01-09 1:36 ` [PATCH 0/4] Quoting HTML-only emails in replies redux Aaron Ecay
2012-01-10 1:53 ` Adam Wolfe Gordon
2012-01-15 9:26 ` David Edmondson
2012-01-16 7:38 ` Aaron Ecay
2012-01-16 8:39 ` David Edmondson
2012-01-16 19:29 ` Jameson Graef Rollins
2012-01-16 22:31 ` Aaron Ecay
2012-01-16 22:42 ` Adam Wolfe Gordon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://notmuchmail.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87k44xgw09.fsf@gmail.com \
--to=dmitry.kurochkin@gmail.com \
--cc=awg@xvx.ca \
--cc=dme@dme.org \
--cc=notmuch@notmuchmail.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://yhetil.org/notmuch.git/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).