From: Max Nikulin <email@example.com>
Subject: Re: [Bug] incorrect indent of next heading after org-paste-subtree
Date: Sun, 1 May 2022 18:09:15 +0700 [thread overview]
Message-ID: <firstname.lastname@example.org> (raw)
On 01/05/2022 09:31, Ihor Radchenko wrote:
> Max Nikulin writes:
>> Another old bug with org-paste-subtree.
>> It make indentation of next heading wrong.
>> Consider the following document and follow described steps:
> I am unable to reproduce on the latest Org.
Thank you, Ihor. I have checked it once more for current main HEAD
2bd34edb64. I can reproduce it using the provided steps in Emacs-26, but
not in Emacs-27.
Unless there is a reason to suspect something weird underneath, the
issue should be considered with rather low priority. Anyway, I have
added trailing newline to generated content and mostly use org-capture
with org-protocol for communication between applications.
next prev parent reply other threads:[~2022-05-01 11:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-30 11:42 Max Nikulin
2022-05-01 2:31 ` Ihor Radchenko
2022-05-01 11:09 ` Max Nikulin [this message]
2022-05-02 4:00 ` Ihor Radchenko
2022-05-02 7:29 ` Max Nikulin
2022-05-02 23:32 ` Samuel Wales
2022-05-03 1:21 ` Ihor Radchenko
2022-07-17 8:52 ` Ihor Radchenko
2022-05-02 1:54 ` Samuel Wales
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:
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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
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).