From: Richard Kim <email@example.com>
To: Bastien <firstname.lastname@example.org>
Cc: Krishan Kharagjitsing <email@example.com>, firstname.lastname@example.org
Subject: Re: Cycling through TODO workflow joins the next line onto the current one
Date: Wed, 23 Sep 2020 06:48:25 -0700 [thread overview]
Message-ID: <email@example.com> (raw)
In-Reply-To: <firstname.lastname@example.org> (Richard Kim's message of "Wed, 23 Sep 2020 06:28:42 -0700")
Richard Kim <email@example.com> writes:
> Bastien <firstname.lastname@example.org> writes:
>> Hi Krishan,
>> Krishan Kharagjitsing <email@example.com> writes:
>>> Hello, I found the following weird behaviour.
>> What is M-x org-version RET ?
> Because of (setq org-log-done 'time) according to
>>> When I set some tasks to DONE and fold the headings with TAB, then
>>> when I cycle back from DONE to TODO it joins the next line with the
>>> current one.
>>> Reproduction guide
>>> Make two TODO headings in org mode
>>> Cycle both TODO items to DONE
>>> Fold the headings (so the dots appear, because the timestamp gets
>>> folded with the heading)
>>> Cycle the first DONE heading
>> Why are there timestamps? Can you provide a test .org file where we
>> can reproduce the problem?
> The original report at the top of
> has gif animation on how this problem can be seen.
On my emacs 27, following demonstrates the problem.
(switch-to-buffer (generate-new-buffer "*demo line joining bug*"))
(setq org-log-done 'time)
(insert "* one\n")
(insert "* two\n")
next prev parent reply other threads:[~2020-09-23 13:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-20 6:37 Cycling through TODO workflow joins the next line onto the current one Krishan Kharagjitsing
2020-09-20 11:56 ` Nicholas Savage
2020-09-23 7:17 ` Bastien
2020-09-23 13:28 ` Richard Kim
2020-09-23 13:48 ` Richard Kim [this message]
2020-09-23 14:22 ` Ihor Radchenko
2020-09-23 23:49 ` Samuel Wales
2020-09-29 3:22 ` Kyle Meyer
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).