emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Rainer M Krug <R.M.Krug@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: Integration of notmuch email references in notes in org-mode
Date: Mon, 18 Feb 2013 16:33:45 +0100	[thread overview]
Message-ID: <512249D9.10002@gmail.com> (raw)
In-Reply-To: <20130218151250.GE18291@kuru.dyndns-at-home.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 18/02/13 16:12, Suvayu Ali wrote:
> Hi Rainer
> 
> On Mon, Feb 18, 2013 at 02:49:32PM +0100, Rainer M Krug wrote:
>> 
>> - From time to time, I have to include email references in notes in org. There is obviously 
>> org-notmuch.el, but I am not to happy with it as, when exporting the notes, the link is shown
>> but neither clickable nor the resulting email is shown in the exported document (both
>> understandable).
>> 
> 
> This has also been an irritation of mine.  I think I will take your second idea (include the
> email on export) and see if I can come-up with a patch for org-notmuch.  Since I'm still a
> newbie elisp programmer, this might take a while.  :-p

If there is a solution in sight, I am happy to wait a bit - email in export, possibly in a block
so that it is set apart from the rest of the document, would be brilliant. Possibly having an
option which can be set to have links exported as links or expanded on export, would be really nice.

> 
>> I could also include a bash source block:
>> 
>> #+header: :results output org #+begin_src sh notmuch show thread:XXXXXXXXXXXXXXXX #+end_src
>> 
>> the result ooks ugly formated - if I use raw, I can not fold the result, due to strange
>> characters at the beginning of the header lines.
> 
> Actually what you see is supposed to be easily parsed.  From the notmuch-show man page:
> 
> --format=(text|json|sexp|mbox|raw)
> 
> text (default for messages)
> 
> The default plain-text format has all text-content MIME parts decoded.  Various components in
> the output, (message, header, body, attachment, and MIME part), will be delimited by 
> easily-parsed markers. Each marker consists of a Control-L character (ASCII decimal 12), the
> name of the marker, and then either an opening or closing brace, ('{' or '}'), to either open 
> or close the component.  For a multipart MIME message, these parts will be nested.
> 
> I'm assuming what you presently see is in text format (default).  Since you are not happy with
> this, I would suggest you try the mbox format.
> 
> [...]
> 
> mbox
> 
> All matching messages are output in the traditional, Unix mbox format with each message being
> prefixed by a line beginning with "From " and a blank line separating each message. Lines in
> the message content beginning with "From " (preceded by zero or more '>' characters) have an
> additional '>' character added.  This reversible escaping is termed "mboxrd" format and
> described in detail here:
> 
> http://homepage.ntlworld.com/jonathan.deboynepollard/FGA/mail-mbox-formats.html
> 

Haven't thought about that - should be straight forward to find a suitable format.

> A quick question though, how do you plan on handling attachments, I presume you want to strip
> them?

Yes - attachments should be included simply as a line "Attachment: NameOfAttachment" - that would
be fine.


Thanks, and I am looking forward to the new additions to org-notmuch,

Rainer

> In that case you will have to parse the output anyway.
> 
> Hope this helps,
> 

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQEcBAEBAgAGBQJRIknZAAoJENvXNx4PUvmCo1AIAI+xSqnxwHLCitiFmPO/wDXV
ygMahUG58s1sy9qDlaKMUmO5GQoHXO9HBFlNyHYt++iBqbUU02LDeCIHbFOv2CT6
Fnzk6SH/eq2sZMIctHju3ybLYYKqV/jJJQwTHEBNjPyywC6IE3cpx0Xftv/xKERw
hKiUttnyucZm3JVoZGLA5kAssq6SAUXFONxaRDekDl4Bch6HNfjoNTSpl4kw0FQz
Jqym+8I8zRMSbrXGyo87KcIM6h3sKTZaeSmAzeuVD3I2E3ovWC2ufbAewLhgpM8P
K8NuR5tURz4DLaoE0Qy9jy0PTZsvzNBt11dB4v9KQHHjIzacGYdiKuWHElLxoc4=
=CMyd
-----END PGP SIGNATURE-----

  reply	other threads:[~2013-02-18 15:34 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-18 13:49 Integration of notmuch email references in notes in org-mode Rainer M Krug
2013-02-18 15:12 ` Suvayu Ali
2013-02-18 15:33   ` Rainer M Krug [this message]
2013-02-18 21:41     ` Including linked emails during export (was Re: Integration of notmuch email references in notes in org-mode) Suvayu Ali
2013-02-19  8:12       ` Rainer M Krug
2013-02-27 13:35         ` Nicolas Goaziou
2013-02-27 13:47           ` Suvayu Ali
2013-02-18 22:02 ` Naive email "referencing" using copy&paste (was: " Karl Voit
2013-02-19  7:59   ` Naive email "referencing" using copy&paste Rainer M Krug

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://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=512249D9.10002@gmail.com \
    --to=r.m.krug@gmail.com \
    --cc=emacs-orgmode@gnu.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://git.savannah.gnu.org/cgit/emacs/org-mode.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).