From: Bastien <bzg@gnu.org>
To: Matt Lundin <mdl@imapmail.org>
Cc: Org Mode List <emacs-orgmode@gnu.org>
Subject: Re: [BUG] incorrect (and slow) indentation of logbook entries
Date: Sat, 05 Sep 2020 17:04:18 +0200 [thread overview]
Message-ID: <878sdofeod.fsf@gnu.org> (raw)
In-Reply-To: <87r1t8sdhd.fsf@fastmail.fm> (Matt Lundin's message of "Sat, 18 Jul 2020 16:46:38 -0500")
Hi Matt,
Matt Lundin <mdl@imapmail.org> writes:
> Commit e3b79ad2bf7ab7b91c0ad2b8383d639bfe154ce7 from Feb. 9, 2020 (Allow
> a new value for `org-adapt-indentation') introduced a bug that causes
> logbooks to be incorrectly indented when promoting an entry.
FWIW, I can confirm this bug, I'll look at it before 9.4.
Thanks for the detailed exploration!
--
Bastien
next prev parent reply other threads:[~2020-09-05 15:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-18 21:46 [BUG] incorrect (and slow) indentation of logbook entries Matt Lundin
2020-07-18 22:24 ` Matt Lundin
2020-09-05 15:04 ` Bastien [this message]
2020-09-07 7:18 ` 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=878sdofeod.fsf@gnu.org \
--to=bzg@gnu.org \
--cc=emacs-orgmode@gnu.org \
--cc=mdl@imapmail.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).