emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Nicolas Goaziou <n.goaziou@gmail.com>
To: Rainer M Krug <r.m.krug@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Including linked emails during export (was Re: Integration of notmuch email references in notes in org-mode)
Date: Wed, 27 Feb 2013 14:35:04 +0100	[thread overview]
Message-ID: <87k3ptswvr.fsf@gmail.com> (raw)
In-Reply-To: <51233407.7070902@gmail.com> (Rainer M. Krug's message of "Tue, 19 Feb 2013 09:12:55 +0100")

Hello,

Rainer M Krug <r.m.krug@gmail.com> writes:

> On 18/02/13 22:41, Suvayu Ali wrote:
>> Hi,
>> 
>> On Mon, Feb 18, 2013 at 04:33:45PM +0100, Rainer M Krug wrote:
>>> On 18/02/13 16:12, Suvayu Ali wrote:
>>>> 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.
>> 
>> The option to open the link is out of the question since different people read their emails
>> differently.  There is no way for a library to get everything right, specially since the link
>> won't be in Emacs. It is in the exported file (e.g. html, pdf, txt).
>
> If I understand the link system correctly, one would need to create a notmuch protocoll so that
> linux can react to clicking the link. But you are right, this is outside org.
>
>
>> 
>> Now to include the email during the export at first I thought it should be possible to write a
>> filter, but then I realised I need to insert an email quote block after whatever parent
>> greater-element holds the link and then redirect the link to this new block.  A filter allows
>> you a way to modify an element, but nothing more.  So I think the correct approach here would
>> be to write a derived backend.  This complicates things quite significantly since now you need
>> to support each backend separately.  I wonder if there is any easier (generic) way to do the
>> above for all present and future backends.
>
> How is the export of links to pictures handled - as far as I remember, if the image is in a LaTeX
> suitable format, the image is included in the LaTeX file, and the same for html. But you are right
> - I guess this is handled in the backend. I don't think that would be a suitable approach as it
> would include to much maintenance.
>
> But what about defining notmuch as a new language for babel, so that one could do the following:
>
> #+begin_src notmuch :exports raw
>   search id:XXXXXXXXXXXXXXXXx
> #+end_src
>
> Would not be much different then
>
> #+begin_src sh :exports raw
>   notmuch search id:XXXXXXXXXXXXXXXXx
> #+end_src
>
> but possibly open more possibilities for customizations?
> XXXXXXXXXXXXXXXXx
> Or inline it could be src_notmuch{search id:XXXXXXXXXXXXXXXXx}
>
> The general advantage would be that one can use the existing infrastructure for code blocks and
>
> Cheers,
>
> Rainer
>
>> 
>> I have CC'd Nicolas, lets see what he has to say.

FWIW, I think the approach suggested by Rainer is good, i.e. writing
a new "language" for Babel, with specific headers. Such blocks would
then be expanded into appropriate Org syntax the exporter can
understand.


Regards,

-- 
Nicolas Goaziou

  reply	other threads:[~2013-02-27 13:35 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
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 [this message]
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=87k3ptswvr.fsf@gmail.com \
    --to=n.goaziou@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=r.m.krug@gmail.com \
    /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).