From: Max Nikulin <email@example.com>
Subject: Re: [Bug] incorrect indent of next heading after org-paste-subtree
Date: Mon, 2 May 2022 14:29:11 +0700 [thread overview]
Message-ID: <firstname.lastname@example.org> (raw)
On 02/05/2022 11:00, Ihor Radchenko wrote:
> Max Nikulin writes:
>>> 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.
> Thanks for the extra info!
> I managed to reproduce using Emacs 26 and it is a real problem with some
> edge case in org-indent. The problem is masked by
> combine-after-change-calls that is used since Emacs 27 but replaced by a
> placeholer in Emacs 26.
> The fix is attached. Let me know if it also works on your side.
I have not performed extensive testing, but your patch fixes the problem
at least with my test file, so thank you for digging into this issue.
next prev parent reply other threads:[~2022-05-02 7:30 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
2022-05-02 4:00 ` Ihor Radchenko
2022-05-02 7:29 ` Max Nikulin [this message]
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).