From: Jeremy Reeve <jeremy.reeve81@gmail.com>
To: Nicolas Goaziou <mail@nicolasgoaziou.fr>
Cc: emacs-orgmode@gnu.org
Subject: Re: Export results of code literal blocks (Jekyll directory structure) xpost emacs.stackexchange
Date: Fri, 30 Jun 2017 13:17:27 +1200 [thread overview]
Message-ID: <CAGdd8vGJWbfqcNYd+y9S04A37nczd51RqQThLX+oPriNLxd3qg@mail.gmail.com> (raw)
In-Reply-To: <87zicsfdr2.fsf@nicolasgoaziou.fr>
On 29 June 2017 at 01:22, Nicolas Goaziou <mail@nicolasgoaziou.fr> wrote:
> Hello,
>
> Jeremy Reeve <jeremy.reeve81@gmail.com> 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
next prev parent reply other threads:[~2017-06-30 1:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-24 23:33 Export results of code literal blocks (Jekyll directory structure) xpost emacs.stackexchange Jeremy Reeve
2017-06-28 13:22 ` Nicolas Goaziou
2017-06-30 1:17 ` Jeremy Reeve [this message]
2017-06-30 7:08 ` Nicolas Goaziou
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=CAGdd8vGJWbfqcNYd+y9S04A37nczd51RqQThLX+oPriNLxd3qg@mail.gmail.com \
--to=jeremy.reeve81@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=mail@nicolasgoaziou.fr \
/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).