From: "Dr. Arne Babenhauserheide" <arne_bab@web.de>
To: emacs-orgmode@gnu.org
Subject: 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: Fri, 28 Aug 2020 15:05:21 +0200 [thread overview]
Message-ID: <871rjqvs32.fsf@web.de> (raw)
[-- Attachment #1: Type: text/plain, Size: 1159 bytes --]
Remember to cover the basics, that is, what you expected to happen and
what in fact did happen. You don't know how to make a good report? See
https://orgmode.org/manual/Feedback.html#Feedback
Your bug report will be posted to the Org mailing list.
------------------------------------------------------------------------
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.
Example:
* new entry
some text * old entry
I tried adding the empty-lines options and empty-lines-before and
empty-lines-after, but this did not fix the problem.
This sometimes causes entries to no longer be recognized as headlines,
so my task planning does not show them (for example in org-agenda view,
clocktable, and kanban.el).
It would be great if it could be ensured that capturing a new entry can
never modify the first line of another entry.
Best wishes,
Arne
--
Unpolitisch sein
heißt politisch sein
ohne es zu merken
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 1076 bytes --]
next reply other threads:[~2020-08-28 13:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-28 13:05 Dr. Arne Babenhauserheide [this message]
2020-08-29 4:49 ` 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/)] Kyle Meyer
2020-08-29 10:36 ` Dr. Arne Babenhauserheide
2020-08-29 12:10 ` Kyle Meyer
2020-09-04 9:28 ` Bastien
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=871rjqvs32.fsf@web.de \
--to=arne_bab@web.de \
--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).