From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jeremy Reeve Subject: Re: Export results of code literal blocks (Jekyll directory structure) xpost emacs.stackexchange Date: Fri, 30 Jun 2017 13:17:27 +1200 Message-ID: References: <87zicsfdr2.fsf@nicolasgoaziou.fr> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:56809) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1dQkYu-0008Jq-0C for emacs-orgmode@gnu.org; Thu, 29 Jun 2017 21:17:33 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1dQkYs-0007HY-Rn for emacs-orgmode@gnu.org; Thu, 29 Jun 2017 21:17:31 -0400 Received: from mail-wr0-x22b.google.com ([2a00:1450:400c:c0c::22b]:35941) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1dQkYs-0007GC-LP for emacs-orgmode@gnu.org; Thu, 29 Jun 2017 21:17:30 -0400 Received: by mail-wr0-x22b.google.com with SMTP id c11so197196596wrc.3 for ; Thu, 29 Jun 2017 18:17:29 -0700 (PDT) In-Reply-To: <87zicsfdr2.fsf@nicolasgoaziou.fr> 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" To: Nicolas Goaziou Cc: emacs-orgmode@gnu.org On 29 June 2017 at 01:22, Nicolas Goaziou wrote: > Hello, > > Jeremy Reeve writes: > >> Org-mode newbie here. Please be gentle. > > Do you have any reason to think we will not be gentle? > > "We have a squeaker today, class. Isn't he cute?" That comment was totally inappropriate for a public mailing list. > > Can't you write a function that fixes generated links? See > `org-export-before-parsing-hook'. Yes I probably can. I can think of many ways of doing exactly that. I wasn't aware of the existence of the hook and that's why I chose to ask. That's what I was looking for - a pointer. Thanks. There seem to be many inconsistencies between the particular versions I am using and the public documentation and I appreciate that the code is probably evolving rapidly. I note the difference in documentation between master in the code repository and what is currently on the public facing web site and that I ought to build the documentation specific to the version I am using. The experience gave me the feeling that there might be something relevant which is not well or at all documented. If I read the entire reference manual of every piece of software I use I would have no time to carry out the actual tasks I use these tools for. It would be morally correct to read the reference manual cover-to-cover to find out the best approach to solving a problem. I think it is unfair to categorise this post as of the 'too lazy to look up something in the manual' form as I had provided a concrete example and what I wanted to achieve and as I tried to hint at - not a highly experienced Emacs-lisp developer or emacs-org user having spent very little time (a day) exposed to org-mode. Occasionally one needs a steer in the right direction, that is all. I think what needs to be appreciated is that there will be a spectrum of users on the one end who are active Emacs-lisp developers who have familiarity with the codebase all the way to people appreciative of the open source efforts but that do not have the time or inclination to act as developers on yet another project unrelated to their work. > >> Also, the above snippet exports everything including the "BEGIN >> export" which I think shouldn't happen but I'll examine that >> separately. > > The closing line is wrong. It should be "#+end_export". Use `M-x > org-lint' to find this kind of problem. Yes. I found this immediately after posting and thanks for the tip about org-lint. Jeremy