From: Ihor Radchenko <yantar92@posteo.net>
To: Farblos <akfkqu.9df7rp@vodafonemail.de>
Cc: emacs-orgmode@gnu.org
Subject: Re: Where does headline data end for the purpose of `org-adapt-indentation´ == ´headline-data
Date: Thu, 08 Jun 2023 11:17:38 +0000 [thread overview]
Message-ID: <87v8fy19v1.fsf@localhost> (raw)
In-Reply-To: <c26685ad-da33-fc44-173f-4c8d9ffedd0f@vodafonemail.de>
Farblos <akfkqu.9df7rp@vodafonemail.de> writes:
> I like the idea of org-adapt-indentation being ´headline-data:
>
> When this variable is set to ‘headline-data’, Org only adapts the
> indentation of the data lines right below the headline, such as
> planning/clock lines and property/logbook drawers.
>
> However, I find the resulting indentation behavior confusing. Before
> reporting bugs, I'd like to know where the headline data ends. I'd
> expect that the first blank (or whitespace-only?) line after a headline
> would end the headline data.
(defun org--at-headline-data-p (&optional beg element)
"Return non-nil when `point' or BEG is inside headline metadata.
Metadata is planning line, properties drawer, logbook drawer right
after property drawer, or clock log line immediately following
properties drawer/planning line/ heading.
Hope it clarifies things.
Note that we had some bugs in this area in older Org versions.
--
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-06-08 11:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-08 10:46 Where does headline data end for the purpose of `org-adapt-indentation´ == ´headline-data Farblos
2023-06-08 11:17 ` Ihor Radchenko [this message]
2023-06-08 20:09 ` Farblos
2023-06-09 7:34 ` Ihor Radchenko
2023-06-10 20:39 ` Jens Schmidt
2023-06-10 20:47 ` Farblos
2023-06-10 20:59 ` Farblos
2023-06-11 10:21 ` Ihor Radchenko
2023-06-11 10:38 ` Farblos
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=87v8fy19v1.fsf@localhost \
--to=yantar92@posteo.net \
--cc=akfkqu.9df7rp@vodafonemail.de \
--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).