From: Ihor Radchenko <yantar92@posteo.net>
To: alain.cochard@unistra.fr
Cc: emacs-orgmode@gnu.org
Subject: Re: org-up-element does not the same for all structural blocks
Date: Mon, 02 Jan 2023 09:24:52 +0000 [thread overview]
Message-ID: <87mt71mgpn.fsf@localhost> (raw)
In-Reply-To: <25522.5360.861501.370084@gargle.gargle.HOWL>
Alain.Cochard@unistra.fr writes:
> With an org file like
>
> * h
> #+begin_export ascii
> foo
> #+end_export
>
> putting the cursor on 'foo' and doing
>
> M-x org-up-element
>
> brings the cursor on '* h'. Same with the following blocks:
>
> ‘#+begin_comment’ ... ‘#+end_comment’
> ‘#+begin_example’ ... ‘#+end_example’
> ‘#+begin_export’ ... ‘#+end_export’
> ‘#+begin_export html’ ... ‘#+end_export’
> ‘#+begin_export latex’ ... ‘#+end_export’
> ‘#+begin_src’ ... ‘#+end_src’ (I tried org and lisp)
> ‘#+begin_verse’ ... ‘#+end_verse’
>
> But for those two blocks:
>
> ‘#+begin_center’ ... ‘#+end_center’
> ‘#+begin_quote’ ... ‘#+end_quote’
>
> the cursor is moved to the beginning of the block instead, which I
> find strange.
This is to be expected. Center blocks, Quote blocks, and special blocks
are "greater elements", which can directly contain other Org elements
inside. Thus,
#+begin_center
Text
#+end_center
is interpreted as
(center-block (paragraph))
So, `org-up-element' with point at paragraph will move to parent
center-block.
In contrast, comment/example/export/src/verse are "lesser blocks", which
cannot contain other Org elements inside - their contents is taken
verbatim:
#+begin_comment
Text
#+end_comment
is interpreted as
(comment-block)
with point at "Text", current element is comment-block, and its parent
is headline in your example.
> Incidentally, is there a definition understandable for the basic user
> of what an "org element" is? I could not find one after a (quick)
> Internet search, not even in
https://orgmode.org/worg/org-syntax.html#orgb8e0d51
Also, see https://orgmode.org/worg/org-syntax.html#Greater_Elements
--
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>
prev parent reply other threads:[~2023-01-02 9:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-01 23:19 org-up-element does not the same for all structural blocks Alain.Cochard
2023-01-02 9:24 ` Ihor Radchenko [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=87mt71mgpn.fsf@localhost \
--to=yantar92@posteo.net \
--cc=alain.cochard@unistra.fr \
--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).