From: Kyle Meyer <email@example.com>
To: "Dr. Arne Babenhauserheide" <firstname.lastname@example.org>
Subject: Re: Bug: org-capture entry sometimes ends without newline, garbles next headline [9.3.6 (9.3.6-elpa @ /home/arne/Disy/.emacs.d/elpa/org-9.3.6/)]
Date: Sat, 29 Aug 2020 00:49:14 -0400 [thread overview]
Message-ID: <email@example.com> (raw)
Dr. Arne Babenhauserheide writes:
> Sometimes when I use org-capture to create a new headline, that headline
> ends with a non-empty partial line that isn’t terminated by a newline.
> This causes the next headline to be corrupted, because the * is appended
> to the last line of the new entry.
I believe this issue has already been resolved on the master branch.
There have been a few bug reports and commits in this area; I think
6882478ca (capture: Fix org-capture-place-entry narrow bounds,
2020-05-29) is the most recent fix.
next prev parent reply other threads:[~2020-08-29 4:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-28 13:05 Bug: org-capture entry sometimes ends without newline, garbles next headline [9.3.6 (9.3.6-elpa @ /home/arne/Disy/.emacs.d/elpa/org-9.3.6/)] Dr. Arne Babenhauserheide
2020-08-29 4:49 ` Kyle Meyer [this message]
2020-08-29 10:36 ` Dr. Arne Babenhauserheide
2020-08-29 12:10 ` Kyle Meyer
2020-09-04 9:28 ` Bastien
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).