From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp0 ([2001:41d0:2:4a6f::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by ms11 with LMTPS id B/HEIP2+sF/8YwAA0tVLHw (envelope-from ) for ; Sun, 15 Nov 2020 05:39:09 +0000 Received: from aspmx1.migadu.com ([2001:41d0:2:4a6f::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp0 with LMTPS id 5c2PHP2+sF9gVAAA1q6Kng (envelope-from ) for ; Sun, 15 Nov 2020 05:39:09 +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 0D36B940416 for ; Sun, 15 Nov 2020 05:39:09 +0000 (UTC) Received: from localhost ([::1]:35890 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1keAkm-0008PP-16 for larch@yhetil.org; Sun, 15 Nov 2020 00:39:08 -0500 Received: from eggs.gnu.org ([2001:470:142:3::10]:38602) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1keAkQ-0008PD-4E for emacs-orgmode@gnu.org; Sun, 15 Nov 2020 00:38:46 -0500 Received: from static.rcdrun.com ([95.85.24.50]:60531) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1keAkN-0002Kv-R1 for emacs-orgmode@gnu.org; Sun, 15 Nov 2020 00:38:45 -0500 Received: from localhost ([::ffff:41.202.241.56]) (AUTH: PLAIN admin, TLS: TLS1.2,256bits,ECDHE_RSA_AES_256_GCM_SHA384) by static.rcdrun.com with ESMTPSA id 00000000002C0004.000000005FB0BEE0.00007887; Sun, 15 Nov 2020 05:38:39 +0000 Date: Sun, 15 Nov 2020 08:38:28 +0300 From: Jean Louis To: Karl Voit , emacs-orgmode@gnu.org, Karl Voit Subject: Re: Changed list indentation behavior: how to revert? Message-ID: References: <2020-11-13T18-23-43@devnull.Karl-Voit.at> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: User-Agent: Mutt/2.0 (3d08634) (2020-11-07) Received-SPF: pass client-ip=95.85.24.50; envelope-from=bugs@gnu.support; helo=static.rcdrun.com X-detected-operating-system: by eggs.gnu.org: First seen = 2020/11/15 00:38:40 X-ACL-Warn: Detected OS = Linux 3.11 and newer [fuzzy] X-Spam_score_int: -18 X-Spam_score: -1.9 X-Spam_bar: - X-Spam_report: (-1.9 / 5.0 requ) BAYES_00=-1.9, SPF_HELO_PASS=-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=none; dmarc=none; 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.01 X-TUID: 42BDQ0F1luf/ * David Rogers [2020-11-15 01:44]: > Hello > > After reading several of the responses to this, I’ve started to wonder: Is > electric-indent-mode broken for everybody because it contains a bug or > design flaw, or is electric-indent-mode working fine but simply not suitable > for every situation? > > In other words, where is the “right” place to fix this problem? It was working in Org file automatically well and fine. As if user decides to indent, electric-indent would help the user: ** HeadingRET At this point below user may decide to indent: - First itemRET after RET ^ - the new line appears here User has to move the cursor to the point shown above for indentation to begin. That is good as user decides it and it is text, it is not programming language with special convention for indentation. Electric indent mode always worked like that, including in Org mode without any problems. The change that is introduced in my opinion, and I did not look into code, is changing how electric indent mode behaves specifically for Org mode as somebody assumes that immediately after headingRET the new lines should be indented, like if there is some special indentation convention for Org mode. So without user deciding to indent, it does following: ** HeadingRET - First line here But there is no indentation convetion for Org mode of that kind that I know. The Org file shown on https://orgmode.org/ does not follow that type of indenting. Common indenting in Org mode is: * Heading Text ** Heading Text *** Heading text Text **** Heading Text here ***** Heading Text ****** Heading Text AND if somebody likes to indent differently electric indent mode would help. Common indenting is not (other may tell me that I am wrong if this statement is wrong) * Heading Text ** Heading Text *** Heading text Text **** Heading Text here ***** Heading Text ****** Heading Text The above change was introduced as default to many users and is not conveniente. Especially not conveniente I find that I need to delete by using backspace all the spaces inserted that I did not want after pressing RET after inserting heading. Some people will insert ONLY heading as a test without any text.