unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: bserrao <bgserrao@gmail.com>
To: notmuch@notmuchmail.org
Subject: Re: Notmuch Emacs reply format=JSON
Date: Mon, 13 Mar 2017 03:32:57 -0700 (MST)	[thread overview]
Message-ID: <CAF8By0VvH9pyTHcb540niP7f1yxwDNKaJ9ZWQ_0-=5=DfEDEwA@mail.gmail.com> (raw)
In-Reply-To: <878tobraw5.fsf@tethera.net>

Well, at work almost everyone uses Outlook (Exchange Server) and send HTML
mails. I've made a script to convert mail to html before sending, but when
replying emacs uses de '>' character has quotation and because of it the
mail gets messed up when i do the conversion.
From what i've read i've concluded that if using the format=json those HTML
pieces were handled differently...maybe i'm wrong. I was just trying to
find a solution/workaround to deal with this.

Thanks, and sorry for my bad english.

Bruno

On Sat, Mar 11, 2017 at 5:17 PM David Bremner-2 [via notmuch] <
ml-node+s198994n4037213h55@n3.nabble.com> wrote:

> bserrao <[hidden email]
> <http:///user/SendEmail.jtp?type=node&node=4037213&i=0>> writes:
>
> > Hello,
> >
> > I need some help in changing the default reply format to JSON in
> > notmuch-emacs.
> > I've looked in the docs and there's this option:
> >
>
> I'm afraid I don't understand what behaviour you want.  Internally
> notmuch-emacs uses --format=sexp to communicate with the CLI, but this
> output contains the same information --format=json.
>
> d
> _______________________________________________
> notmuch mailing list
> [hidden email] <http:///user/SendEmail.jtp?type=node&node=4037213&i=1>
> https://notmuchmail.org/mailman/listinfo/notmuch
>
>
> ------------------------------
> If you reply to this email, your message will be added to the discussion
> below:
>
> http://notmuch.198994.n3.nabble.com/Notmuch-Emacs-reply-format-JSON-tp4037188p4037213.html
> To unsubscribe from Notmuch Emacs reply format=JSON, click here
> <http://notmuch.198994.n3.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=4037188&code=YmdzZXJyYW9AZ21haWwuY29tfDQwMzcxODh8LTIxMzM3MDk4MTg=>
> .
> NAML
> <http://notmuch.198994.n3.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>
>




--
View this message in context: http://notmuch.198994.n3.nabble.com/Notmuch-Emacs-reply-format-JSON-tp4037188p4037238.html
Sent from the notmuch mailing list archive at Nabble.com.

  reply	other threads:[~2017-03-13 10:33 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-10 10:27 Notmuch Emacs reply format=JSON bserrao
2017-03-11 17:17 ` David Bremner
2017-03-13 10:32   ` bserrao [this message]
2017-03-13 11:28     ` David Bremner
2017-03-13 17:00     ` Brian Sniffen
2017-03-21 16:43       ` bserrao

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='CAF8By0VvH9pyTHcb540niP7f1yxwDNKaJ9ZWQ_0-=5=DfEDEwA@mail.gmail.com' \
    --to=bgserrao@gmail.com \
    --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).