From: cedric simon <simonced@gmail.com>
To: Kaushal Modi <kaushal.modi@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Orgmode 9.09 and export of source blocks
Date: Sat, 1 Jul 2017 10:45:23 +0900 [thread overview]
Message-ID: <CAMYRq8b5VjDj6Cyb-3ZC2=b6JUMB5OFPJJoLOaj7CHhyopCYUQ@mail.gmail.com> (raw)
In-Reply-To: <CAFyQvY3xgXowmiKO3GOajMjCrhbqB1KQsbo+zLG7o5sUj9j2pQ@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1980 bytes --]
Hi,
thank you very much for your explanations about properties inheritances, I
didn't know much about them.
So I managed to solve my problem buy using a property drawer
~header-args:sql:~ so it doesn't override my ~#+PROPERTY~ that I set
globally.
I'll give some tries with org-eldoc, seems an interresting package I didn't
know about.
Thank you very much again for your help!
2017-06-30 13:46 GMT+09:00 Kaushal Modi <kaushal.modi@gmail.com>:
> On Thu, Jun 29, 2017 at 11:30 PM cedric simon <simonced@gmail.com> wrote:
>
>> Hi everyone,
>>
>> I work with org mode for writing all my documentation and use source code
>> blocks extensively.
>> I don't know if I found a bug or something, but I encounter a strange
>> behavior with SQL source blocks.
>> Despite the settings I apply, they are always evaluated if I have
>> ":exports both" set.
>>
>> I made a reproducible document, it's on gist, if you have time please
>> have a look:
>> https://gist.github.com/simonced/2a4ee29ed779a563b9fb7a9d8dcc83cf
>>
>
> From what I understand, the values you set in "#+PROPERTY: header-args" is
> not inherited further down once you use a ":header-args:" property drawer
> (even when org-use-property-inheritance is set to t).
>
> I made up an elaborate example and have put it up here[1], that explains
> when the header-args values set in #+PROPERTY or PROPERTY drawer are
> effective.
>
> In addition, using the org-eldoc package[2] (in Org contrib) helps a lot
> in seeing the effective header-args values for a given source block. Just
> put the cursor on the BEGIN_SRC line and you will see it all :)
>
> Example:
>
> [image: image.png]
>
>
> [1]: https://gist.githubusercontent.com/kaushalmodi/
> 4be9fb4e460adb197a6a23ffc3557665/raw/4fcc33641ed33141dc6e205fc2435f
> 06ddeef4e6/header-arg-prop-inheritance.org
> [2]: http://orgmode.org/cgit.cgi/org-mode.git/log/contrib/
> lisp/org-eldoc.el
> --
>
> Kaushal Modi
>
--
Cedric Simon <http://www.google.com/profiles/simonced>
[-- Attachment #1.2: Type: text/html, Size: 3731 bytes --]
[-- Attachment #2: image.png --]
[-- Type: image/png, Size: 136579 bytes --]
prev parent reply other threads:[~2017-07-01 1:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-30 3:29 Orgmode 9.09 and export of source blocks cedric simon
2017-06-30 4:46 ` Kaushal Modi
2017-07-01 1:45 ` cedric simon [this message]
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='CAMYRq8b5VjDj6Cyb-3ZC2=b6JUMB5OFPJJoLOaj7CHhyopCYUQ@mail.gmail.com' \
--to=simonced@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=kaushal.modi@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).