emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Nick Dokos <ndokos@gmail.com>
To: emacs-orgmode@gnu.org
Subject: [BUG] Dynamic blocks not recognized by org-element
Date: Tue, 26 Apr 2022 02:53:03 -0400	[thread overview]
Message-ID: <aee88a16-6d55-9c3d-6de3-941e42acffa0@gmail.com> (raw)

Starting with `emacs -Q', I create a simple file with the following 
contents:

--8<---------------cut here---------------start------------->8---
* Clocktable

#+BEGIN: clocktable :maxlevel 3 :emphasize nil :scope file
#+END: clocktable
--8<---------------cut here---------------end--------------->8---

I position the cursor on the #+BEGIN line and evaluate
`(org-element-at-point)'. I expected to get a dynamic-block, but I get a
paragraph:

(paragraph
  (:begin 15 :end 74 :contents-begin 15 :contents-end 74 :post-blank 0 
:post-affiliated 15 :mode planning :granularity element :parent
          (section
           (:begin 15 :end 92 :contents-begin 15 :contents-end 92 
:robust-begin 15 :robust-end 90 :post-blank 0 :post-affiliated 15 :mode 
section :granularity element :parent
                   (headline
                    (:raw-value "Clocktable" :begin 1 :end 92 :pre-blank 
1 :contents-begin 15 :contents-end 92 :robust-begin 17 :robust-end 90 
:level 1 :priority nil :tags nil :todo-keyword nil :todo-type nil 
:post-blank 0 :footnote-section-p nil :archivedp nil :commentedp nil 
:post-affiliated 1 :title "Clocktable"))))))

Looks like a bug to me.


Emacs  : GNU Emacs 29.0.50 (build 1, x86_64-pc-linux-gnu, GTK+ Version 
3.24.31, cairo version 1.17.4) of 2022-02-12
Package: Org mode version 9.5.3 (release_9.5.3-452-g407104 @ 
/home/nick/src/emacs/org/org-mode/lisp/)
-- 
Nick




             reply	other threads:[~2022-04-26  6:55 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-26  6:53 Nick Dokos [this message]
2022-04-26  7:14 ` [BUG] Dynamic blocks not recognized by org-element Ihor Radchenko
2022-04-26  7:38   ` Nick Dokos

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=aee88a16-6d55-9c3d-6de3-941e42acffa0@gmail.com \
    --to=ndokos@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    /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).