From: Farblos <akfkqu.9df7rp@vodafonemail.de>
To: emacs-orgmode@gnu.org
Subject: Where does headline data end for the purpose of `org-adapt-indentation´ == ´headline-data
Date: Thu, 8 Jun 2023 12:46:15 +0200 [thread overview]
Message-ID: <c26685ad-da33-fc44-173f-4c8d9ffedd0f@vodafonemail.de> (raw)
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.
Below are some examples where to I think headline data expands ("<=="
pointing to point, underscore indicating trailing blanks). Probably
somebody could correct or confirm.
Thanks!
** Headline 1
<== in headline data ==
** Headline 2
:properties:
<== in headline data ==
** Headline 3
:properties:
:custom_id: foo
:end:
:logbook:
clock: [2023-06-08 Thu 12:34]--[2023-06-08 Thu 12:36] => 0:02
:end:
<== in headline data ==
** Headline 4
:properties:
<== out of headline data
** Headline 5
:properties:
___
<== out of headline data (previous line containing three blanks)
next reply other threads:[~2023-06-08 10:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-08 10:46 Farblos [this message]
2023-06-08 11:17 ` Where does headline data end for the purpose of `org-adapt-indentation´ == ´headline-data Ihor Radchenko
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=c26685ad-da33-fc44-173f-4c8d9ffedd0f@vodafonemail.de \
--to=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).