From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nicolas Goaziou 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 Message-ID: <87k3ptswvr.fsf@gmail.com> References: <5122316C.7070706@gmail.com> <20130218151250.GE18291@kuru.dyndns-at-home.com> <512249D9.10002@gmail.com> <20130218214125.GC25900@kuru.dyndns-at-home.com> <51233407.7070902@gmail.com> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([208.118.235.92]:36951) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UAhAP-0007j1-Je for emacs-orgmode@gnu.org; Wed, 27 Feb 2013 08:35:33 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1UAhAK-0002DL-JK for emacs-orgmode@gnu.org; Wed, 27 Feb 2013 08:35:29 -0500 Received: from mail-wg0-f45.google.com ([74.125.82.45]:52395) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UAhAK-0002DD-D0 for emacs-orgmode@gnu.org; Wed, 27 Feb 2013 08:35:24 -0500 Received: by mail-wg0-f45.google.com with SMTP id dq12so473744wgb.24 for ; Wed, 27 Feb 2013 05:35:23 -0800 (PST) In-Reply-To: <51233407.7070902@gmail.com> (Rainer M. Krug's message of "Tue, 19 Feb 2013 09:12:55 +0100") List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Rainer M Krug Cc: emacs-orgmode@gnu.org Hello, Rainer M Krug 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