emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed

From: Ihor Radchenko <yantar92@posteo.net>
To: note meta <metanote.team@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Some Issues I Encountered While Developing Metanote
Date: Tue, 12 Sep 2023 08:16:47 +0000	[thread overview]
Message-ID: <87msxriz68.fsf@localhost> (raw)
In-Reply-To: <CAMCUW+vYVv6OsvoJ+_mC8Gajygp0f+fCPOOThhhHa58aeo3eNQ@mail.gmail.com>

note meta <metanote.team@gmail.com> writes:

> 1. Dynamic Block Parsing Issue
>
>    #+begin_example
> #+begin
> #+end:
>    #+end_example
>
>    The above is a Dynamic Block, and the parsed syntax tree is:
>
>    (org-data nil (section (:begin 1 :end 17 :contents-begin 1 :contents-end
> 17 :post-blank 0 :post-affiliated 1 :parent #0) (dynamic-block (:begin 1
> :end 17 :block-name nil :arguments nil :contents-begin nil :contents-end
> nil :post-blank 0 :post-affiliated 1 :parent #1))))

Are you sure that you meant

#+begin
#+end:

Maybe

#+begin:
#+end:
?

Either way, there is no dynamic block in both cases - dynamic blocks
must have non-empty NAME. See
https://orgmode.org/worg/org-syntax.html#Dynamic_Blocks

-- 
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>

next prev parent reply	other threads:[~2023-09-12  8:17 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-11 12:04 Some Issues I Encountered While Developing Metanote note meta
2023-09-12  8:16 ` Ihor Radchenko [this message]
     [not found]   ` <CAMCUW+utUvpwkjzP4wcBLfwsuoV-8VN=v05xuZKj57jSq_k8RA@mail.gmail.com>
2023-09-12 10:10     ` Ihor Radchenko
2023-09-12  8:23 ` [BUG] org-element-paragraph-separate is not accurate when detecting table.el tables (was: Some Issues I Encountered While Developing Metanote) Ihor Radchenko
2023-09-12  8:43 ` Some Issues I Encountered While Developing Metanote Ihor Radchenko
2023-09-12  8:54 ` Ihor Radchenko

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=87msxriz68.fsf@localhost \
    --to=yantar92@posteo.net \
    --cc=emacs-orgmode@gnu.org \
    --cc=metanote.team@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

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).