From: Bastien <firstname.lastname@example.org>
To: Kyle Meyer <email@example.com>
Cc: Tim Cross <firstname.lastname@example.org>, email@example.com
Subject: Re: org-adapt-indentation not honored prior to Org 9.4?
Date: Wed, 31 Mar 2021 10:53:18 +0200 [thread overview]
Message-ID: <firstname.lastname@example.org> (raw)
In-Reply-To: <email@example.com> (Kyle Meyer's message of "Wed, 31 Mar 2021 00:14:06 -0400")
Kyle Meyer <firstname.lastname@example.org> writes:
> Tim Cross writes:
>> one thing I think might help (maybe too late) would be to put the
>> entries for both electric-indent-mode and org-adapt-indentation so that
>> they are together in the release notes as they do interact with each
>> other and often people stop looking once they see one and not the other
>> (they are currently a fair 'distance' apart in the file).
> Thanks for the suggestion. I'm not sure that it will help, but it's
> easy to do, at least in the Git repo [*], so I've done so in
Thanks for doing this.
> [*] That of course won't be in effect for the file included with Emacs
> 27.2. It also won't be at <https://orgmode.org/Changes.html>.
> Cc'ing Bastien in case he thinks updating 9.4's Changes.html is
> worth it.
The overall discussion convinced me that `nil' is probably a better
default for `org-adapt-indentation' (instead of `t') so I suggest we
wait for the 9.5 changelog to promote these clarifications.
(I generally don't like the idea of revising the changelog after the
release even if we had and may well accept exceptions.)
prev parent reply other threads:[~2021-03-31 8:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-22 19:37 org-adapt-indentation not honored prior to Org 9.4? Mike Kupfer
2021-03-24 14:08 ` TRS-80
2021-03-24 14:45 ` Maxim Nikulin
2021-03-30 3:38 ` Kyle Meyer
2021-03-30 4:21 ` Tim Cross
2021-03-31 4:14 ` Kyle Meyer
2021-03-31 8:53 ` Bastien [this message]
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).