From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp1 ([2001:41d0:2:4a6f::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by ms11 with LMTPS id fX29C94osl9zcgAA0tVLHw (envelope-from ) for ; Mon, 16 Nov 2020 07:23:10 +0000 Received: from aspmx1.migadu.com ([2001:41d0:2:4a6f::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp1 with LMTPS id uC5iB94osl8aYwAAbx9fmQ (envelope-from ) for ; Mon, 16 Nov 2020 07:23:10 +0000 Received: from lists.gnu.org (lists.gnu.org [209.51.188.17]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by aspmx1.migadu.com (Postfix) with ESMTPS id 933959400D3 for ; Mon, 16 Nov 2020 07:23:09 +0000 (UTC) Received: from localhost ([::1]:37260 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1keYqy-0001G5-8B for larch@yhetil.org; Mon, 16 Nov 2020 02:23:08 -0500 Received: from eggs.gnu.org ([2001:470:142:3::10]:41728) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1keYqX-0001Fx-F2 for emacs-orgmode@gnu.org; Mon, 16 Nov 2020 02:22:41 -0500 Received: from mail-pf1-x42f.google.com ([2607:f8b0:4864:20::42f]:44027) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1keYqU-0003AB-MJ for emacs-orgmode@gnu.org; Mon, 16 Nov 2020 02:22:41 -0500 Received: by mail-pf1-x42f.google.com with SMTP id z3so13298995pfb.10 for ; Sun, 15 Nov 2020 23:22:37 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=references:user-agent:from:to:subject:in-reply-to:message-id:date :mime-version:content-transfer-encoding; bh=jx+NOCk55Tl1V1m6MoLfZB+oRdtUbyaq11ByrTZY8Io=; b=RUVlp2sKjIP9rYOCJkkb2lnPpwytZ2Se/ICWmO3+cWmNEWiacpZnfw26n1H5c4CgT4 YGfVeaM0tEQAAbeWBZ9MQNhgQRVGI3G7Oozjp+zuuZHEbK9pg5BTjJyeg/m3Hv6I94V8 FaGBLa53weIIgpDzFuOiqRqw/slXmBoW/PHbRa3iYHdAhjA9bXBPD8mUXR9BPomVoS9J K4y0NId7HUuzhOAMS4xLMX7sJ2w8r+n/NnYBA52vtCu/jTTNfg3Mvvhoxg7gyHtUQDAS W+fZUJpq9pFBFz4qg/S8y1aAHrjXAdmr2Dm20PNCgxNzDQZ/iKfdjmmCPVKmFhNYgyIg 21IQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:references:user-agent:from:to:subject :in-reply-to:message-id:date:mime-version:content-transfer-encoding; bh=jx+NOCk55Tl1V1m6MoLfZB+oRdtUbyaq11ByrTZY8Io=; b=tovnvgCsirea2/Uj0fmaZAn6UImM4CuzLwlAHr5Iza4qeyzcXLsVfSbrKzJF+oy3s4 tt8sHTIgoMxWrRvX51TfTNomZ19VExVCl8wPlIlK5O81v2H26mpHRJ1gROAw6RCo0Gjb Y+gb87aU93W+SR5vU4Zwl4VJKkJAUqdSp+v2RgNLPEL3YDhryBhsAjx1y/woI4dFluKK YdFOMOAxu4cDoaiVVe0Y8U0ttmn2QgIHpPhMcbXirWPuTHLNgBnjeLJD9wwEeZbdwPfV S9it9mqnJdjvzoq69sVRiDGFMU7eeCaS8tNIKNWXAbyLuaysEn9EIP1jXlmJYkIHBfzK tYOQ== X-Gm-Message-State: AOAM531L975wwksY1/VlDM4SIAsKDKz+IDZtNHbUdigevnkAwdAqQ06n FI8Nnnahl8pma0GNa5RfDIDaIfn3crlywg== X-Google-Smtp-Source: ABdhPJzHf5yrzlZ/b1HzxbiDaGhlQawaGbDXKeXeyIzW8DrYZlIcqP3HO2orkwSCF1po5N0nOXfJ1w== X-Received: by 2002:a63:fe0c:: with SMTP id p12mr11805356pgh.31.1605511356397; Sun, 15 Nov 2020 23:22:36 -0800 (PST) Received: from tim-desktop (220-235-14-97.dyn.iinet.net.au. [220.235.14.97]) by smtp.gmail.com with ESMTPSA id w131sm16963603pfd.14.2020.11.15.23.22.34 for (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Sun, 15 Nov 2020 23:22:35 -0800 (PST) References: <2020-11-13T18-23-43@devnull.Karl-Voit.at> <874klqew77.fsf@web.de> <20201115122154.50ad1503@linux-h0yu.fritz.box> <87tutq67ka.fsf@gmail.com> <87tutpvppm.fsf@kyleam.com> <871rgtwzrs.fsf@web.de> User-agent: mu4e 1.5.7; emacs 27.1.50 From: Tim Cross To: emacs-orgmode@gnu.org Subject: Re: Changed list indentation behavior: how to revert? In-reply-to: <871rgtwzrs.fsf@web.de> Message-ID: <87y2j1ahqf.fsf@gmail.com> Date: Mon, 16 Nov 2020 18:22:32 +1100 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Received-SPF: pass client-ip=2607:f8b0:4864:20::42f; envelope-from=theophilusx@gmail.com; helo=mail-pf1-x42f.google.com X-detected-operating-system: by eggs.gnu.org: No matching host in p0f cache. That's all we know. X-Spam_score_int: -20 X-Spam_score: -2.1 X-Spam_bar: -- X-Spam_report: (-2.1 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: emacs-orgmode@gnu.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+larch=yhetil.org@gnu.org Sender: "Emacs-orgmode" X-Scanner: ns3122888.ip-94-23-21.eu Authentication-Results: aspmx1.migadu.com; dkim=pass header.d=gmail.com header.s=20161025 header.b=RUVlp2sK; dmarc=pass (policy=none) header.from=gmail.com; spf=pass (aspmx1.migadu.com: domain of emacs-orgmode-bounces@gnu.org designates 209.51.188.17 as permitted sender) smtp.mailfrom=emacs-orgmode-bounces@gnu.org X-Spam-Score: -0.71 X-TUID: Jp9CWOhB6y+L Dr. Arne Babenhauserheide writes: > Kyle Meyer writes: >> So, it seems that changing Org to honor electric-indent-mode is now >> making some users aware of org-adapt-indentation and that its default >> value is not what they want. > > I=E2=80=99ve seen before that increasing the depth of a headline with M-= =E2=86=92 > indents all its content. That was mildly annoying, but nothing to worry > about. > > It=E2=80=99s the change to the behavior of RET that disturbs my writing f= low. > Now I always have to hit RET twice, or hit RET C-a to start typing. > > It=E2=80=99s not just about the default, it is about long-standing muscle= memory > suddenly being wrong. This breaks my workflow on an update and requires > me to start digging to find out how to get my system back into a good > state. > > That=E2=80=99s something which makes me nervous, because I often don=E2= =80=99t have the > time or energy to investigate when something breaks, so when that > workflow is broken, I=E2=80=99m bound to operate on a broken workflow for > anything from days to months, because I cannot estimate how much time > will be required to fix it (and at work I should not just take 3 hours > off to search for some configuration value). > Hi Arne, I can completely understand your position. However, I wanted to point out that this change was documented in the org NEWS file, where all version changes are documented. When upgrading to a new version of org, everyone should look there, ideally before the upgrade or soon afterwards and definitely when you notice some changed behaviour. It will save hours of trouble shooting and often tells you how to restore previous behaviour. A very under appreciated piece of valuable documentation. Tim -- Tim Cross