emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: "Göktuğ Kayaalp" <self@gkayaalp.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Inheriting some local variables from source code block editing buffers
Date: Mon, 14 May 2018 18:47:52 +0200	[thread overview]
Message-ID: <87d0xyxjyf.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <ygmfu2ui4bk.fsf@gkayaalp.com> ("Göktuğ Kayaalp"'s message of "Mon, 14 May 2018 19:34:39 +0300")

Göktuğ Kayaalp <self@gkayaalp.com> writes:

> The attr was meant for BEGIN_EXPORT blocks because it seems to me that
> an equivalent of ‘org-babel-get-src-block-info’ does not exist for those
> blocks, and that function _only_ works with BEGIN_SRC blocks.  Is there
> a function available or would I have to write one to do this?

With the following example:

   #+header: :foo bar
   #+begin_export latex
   Foo
   #+end_export

(org-element-property :header (org-element-at-point)) => (":foo bar")

and

(cl-mapcan #'org-babel-parse-header-arguments
           (org-element-property :header (org-element-at-point)))

=>

((:foo . "bar"))


> Looking all over the Org manual searching for BEGIN_(LATEX|HTML), I
> haven't seen once a header argument used with a block that is not a
> BEGIN_SRC block, in neither of the forms.  And none of the ‘org-edit-*’
> functions apart from ‘org-edit-src-code’ in org-src.el seem to process
> header arguments, and nor does ‘org-src--edit-element’.

True, but this is also true for "attr_...".

> I can't find any documentation on Org-mode's internal APIs and how
> different parts fit together, so I'm having to figure things out reading
> source code.

See <https://orgmode.org/worg/dev/org-element-api.html>.

  reply	other threads:[~2018-05-14 16:48 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-29 17:19 Inheriting some local variables from source code block editing buffers Göktuğ Kayaalp
2018-04-29 22:09 ` Bastien
2018-05-01  3:30   ` Göktuğ Kayaalp
2018-05-01  8:43     ` Nicolas Goaziou
2018-05-01  8:45       ` Nicolas Goaziou
2018-05-01 11:41       ` Göktuğ Kayaalp
2018-05-01 11:55         ` Nicolas Goaziou
     [not found]           ` <ygmvac7lcl1.fsf@gkayaalp.com>
2018-05-01 14:00             ` Nicolas Goaziou
2018-05-01 16:37           ` Aaron Ecay
     [not found]             ` <ygmin87kwua.fsf@gkayaalp.com>
2018-05-01 19:35               ` Aaron Ecay
2018-05-01 20:04                 ` Göktuğ Kayaalp
2018-05-01 20:53                   ` Aaron Ecay
2018-05-01 22:12                     ` Göktuğ Kayaalp
2018-05-01 22:19                       ` Aaron Ecay
2018-05-01 22:26                       ` Göktuğ Kayaalp
2018-05-02 10:16                         ` Nicolas Goaziou
2018-05-02 19:52                           ` Göktuğ Kayaalp
2018-05-01 11:45       ` Göktuğ Kayaalp
2018-05-14  5:44 ` Göktuğ Kayaalp
2018-05-14 12:13   ` Nicolas Goaziou
2018-05-14 16:34     ` Göktuğ Kayaalp
2018-05-14 16:47       ` Nicolas Goaziou [this message]
2018-05-15 18:36         ` Göktuğ Kayaalp
2018-05-18 21:48           ` Göktuğ Kayaalp
2018-05-19 12:26             ` Nicolas Goaziou
2018-05-21 14:20             ` Aaron Ecay
2018-05-14 13:33   ` Aaron Ecay
2018-05-14 16:46     ` Göktuğ Kayaalp

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=87d0xyxjyf.fsf@nicolasgoaziou.fr \
    --to=mail@nicolasgoaziou.fr \
    --cc=emacs-orgmode@gnu.org \
    --cc=self@gkayaalp.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).