From: Michael Dauer <mick.dauer@gmail.com>
To: Ihor Radchenko <yantar92@posteo.net>
Cc: emacs-orgmode@gnu.org
Subject: Re: BUG: (org-insert-subheading) fails when on true begin of line (first star) of heading
Date: Fri, 12 May 2023 12:27:59 +0200 [thread overview]
Message-ID: <CAP7OBxJiDRovxYjMBrT8H-dUecw6_W2MAR80KRPe3jM69M5wKQ@mail.gmail.com> (raw)
In-Reply-To: <87wn1f41ji.fsf@localhost>
[-- Attachment #1: Type: text/plain, Size: 2141 bytes --]
I understand that it's behavior is derived from org-insert-heading. But IMO
that does not make sense for this function, advice all that it is taking
the current indentation level as basis to devote the new heading as child
of the previous heading. It e.g. created a "orphan" grand child instead of
a child.
Not important for me, just strangely non-intuitive.
Ihor Radchenko <yantar92@posteo.net> schrieb am Do., 11. Mai 2023, 12:11:
> Michael Dauer <mick.dauer@gmail.com> writes:
>
> > Example
> > * h1
> > <>** h11
> >
> > brings:
> > * h1
> > *** <>
> > ** h11
>
> This is expected. `org-insert-subheading' inherits what
> `org-insert-heading' does:
>
> Insert a new heading or an item with the same depth at point.
>
> ***************************************************************
> If point is at the beginning of a heading, insert a new heading
> or a new headline above the current one. When at the beginning
> of a regular line of text, turn it into a heading.
> ***************************************************************
>
> If point is in the middle of a line, split it and create a new
> headline with the text in the current line after point (see
> org-M-RET-may-split-line on how to modify this behavior). As
> a special case, on a headline, splitting can only happen on the
> title itself. E.g., this excludes breaking stars or tags.
>
> With a C-u prefix, set org-insert-heading-respect-content to
> a non-nil value for the duration of the command. This forces the
> insertion of a heading after the current subtree, independently
> on the location of point.
>
> With a C-u C-u prefix, insert the heading at the end of the tree
> above the current heading. For example, if point is within a
> 2nd-level heading, then it will insert a 2nd-level heading at
> the end of the 1st-level parent subtree.
>
> --
> 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>
>
[-- Attachment #2: Type: text/html, Size: 3052 bytes --]
next prev parent reply other threads:[~2023-05-12 10:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-11 8:06 BUG: (org-insert-subheading) fails when on true begin of line (first star) of heading Michael Dauer
2023-05-11 10:15 ` Ihor Radchenko
2023-05-12 10:27 ` Michael Dauer [this message]
2023-05-13 10:17 ` Ihor Radchenko
2024-02-10 16:01 ` 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=CAP7OBxJiDRovxYjMBrT8H-dUecw6_W2MAR80KRPe3jM69M5wKQ@mail.gmail.com \
--to=mick.dauer@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=yantar92@posteo.net \
/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).