From: Gustavo Barros <gusbrs.2016@gmail.com>
To: Bastien <bzg@gnu.org>
Cc: emacs-orgmode@gnu.org
Subject: Re: Bug: org-insert-heading-respect-content before first heading [9.4 (9.4-19-gb1de0c-elpaplus @ /home/gustavo/.emacs.d/elpa/org-plus-contrib-20201019/)]
Date: Sun, 02 May 2021 00:07:45 -0300 [thread overview]
Message-ID: <87eeepzvcu.fsf@gmail.com> (raw)
In-Reply-To: <87bl9ufnnh.fsf@gnu.org>
Hi Bastien,
On Sat, 01 May 2021 at 13:02, Bastien <bzg@gnu.org> wrote:
> Hi Gustavo,
>
> Gustavo Barros <gusbrs.2016@gmail.com> writes:
>
>> I just found a misbehaving of `org-insert-heading-respect-content':
>> when
>> it's called before the first heading in the buffer, it breaks the
>> structure of that fist heading by inserting a new heading on the line
>> the previous heading existed.
>
> Fixed with commit fb3030188 in the maint branch, thanks a lot.
>
> Please test it and report any problem you may encounter.
Thank you very much.
I just tested the fix and, indeed, `org-insert-heading-respect-content'
no longer breaks the structure of the first heading. However, if I may
add a nitpick, the value of `org-blank-before-new-entry' does not seem
to be honored in this case. For default values, a distance of one blank
line is ensured to the next heading. In the report's ECM, after the
fix, the new heading is inserted immediately before it. (I'm not sure
it is really `org-blank-before-new-entry' which is at play here, but the
behavior is not the same before the first heading than it is after it,
with respect to blank lines).
Best,
Gustavo.
next prev parent reply other threads:[~2021-05-02 3:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-21 14:18 Bug: org-insert-heading-respect-content before first heading [9.4 (9.4-19-gb1de0c-elpaplus @ /home/gustavo/.emacs.d/elpa/org-plus-contrib-20201019/)] Gustavo Barros
2021-05-01 16:02 ` Bastien
2021-05-02 3:07 ` Gustavo Barros [this message]
2021-05-02 6:54 ` Bastien
2021-05-02 17:11 ` Gustavo Barros
2021-05-06 11:53 ` Bastien
2021-05-06 12:15 ` Gustavo Barros
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=87eeepzvcu.fsf@gmail.com \
--to=gusbrs.2016@gmail.com \
--cc=bzg@gnu.org \
--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).