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 aFM6I5wjsV+dGgAA0tVLHw (envelope-from ) for ; Sun, 15 Nov 2020 12:48:28 +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 cMf5HpwjsV9heAAAbx9fmQ (envelope-from ) for ; Sun, 15 Nov 2020 12:48:28 +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 248FE94050F for ; Sun, 15 Nov 2020 12:48:28 +0000 (UTC) Received: from localhost ([::1]:41116 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1keHSF-0003gX-52 for larch@yhetil.org; Sun, 15 Nov 2020 07:48:27 -0500 Received: from eggs.gnu.org ([2001:470:142:3::10]:38238) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1keHPV-0001xy-8c for emacs-orgmode@gnu.org; Sun, 15 Nov 2020 07:45:37 -0500 Received: from static.rcdrun.com ([95.85.24.50]:46677) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1keHPO-0005ii-Hp for emacs-orgmode@gnu.org; Sun, 15 Nov 2020 07:45:33 -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 00000000002C000F.000000005FB122C9.00004552; Sun, 15 Nov 2020 12:44:56 +0000 Date: Sun, 15 Nov 2020 15:09:53 +0300 From: Jean Louis To: Gustavo Barros Subject: Re: Changed list indentation behavior: how to revert? Message-ID: References: <665024.1605436621@apollo2.minshall.org> <87y2j2u9g7.fsf@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Content-Disposition: inline In-Reply-To: <87y2j2u9g7.fsf@gmail.com> 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 07:44:41 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: , Cc: Greg Minshall , David Rogers , Karl Voit , emacs-orgmode@gnu.org, Karl Voit 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.49 X-TUID: 44qVx/23YOZF * Gustavo Barros [2020-11-15 14:49]: :PROPERTIES: :CREATED: [2020-11-15 Sun 15:09] :ID: fef3cdfd-8870-4471-bcc7-4d690bfaceb2 :END: > I'm quite surprised by the reaction to this issue, because > `electric-indent-mode' *does not change Org's indentation settings*, it > just applies them alongside RET. Which makes me think that those who've > been so bitten by it where actually manually overriding (their own) > settings in this area by never applying indentation. If that's your > case, you'd probably be very surprised of running `org-indent-region' in > your documents (don't do it, I don't want to break them). > > In particular, one "surprising" result of the "new behavior" is that of > indentation after a heading. That was already and continues to be > controlled by the user option `org-adapt-indentation'. If you don't > want your content to be indented after a heading, set it to nil. And > `electric-indent-mode' should do what you expect in this regard. That is useful. What is not useful is introducing default to thousands of users without asking at least 1% of them. I have 2456 Org files on my system and inconsistency introduced only on my system also affects people like me and those who receive Org files produced on my system. What about other users among 1% of them... I propose that NEWS and Info files shall include pointers from indentation descriptions to that option, as authors considered including function to turn off electric indent mode, while it is now obvious that this function here already does the work. So documentation and NEWS shall be updated. > An example from Greg: > > > ----- > > * i wanted a headline > > * i wanted a subhead, but it's ignored by org mode > > ----- > > That's because the first one is indeed a heading, and the second is not, > it is a plain list item. By definition a heading must start at the > left margin. That I did not know. Maybe I remember wrong but back in time even indented headings worked. Now I have tested it they do not work, so they need to be on the first column on left side. Side thought: what about hebrew and arabic, how does Org mode work for those languages? > You (plural) could probably also get some juice from looking into, and > incorporating to muscle memory, `M-RET', `C-RET' and `C-j'. I do, thank you for reminder. Us in plural are sometimes teachers or mentors who educate other people who are supposed to edit Org files in most simple manner, and those people will never be able to write to this list to find out which option where, not even to know about indentation things. When default is introduced then all people following an educator has to turn off default. They will not even know why. One default introduced can cause butterfly effect. General design of user interface should not conquer their habits unless substantial amount of users have demanded it so. > Of course, with that said, if you really don't like > `electric-indent-mode' for Org, you can disable it as described in > the Org News, previously linked to in this thread. There is ground > to prefer this, particularly for the list case, mentioned by Karl in > the original message of this thread. But `electric-indent-mode' > does not induce a new pattern of indentation for Org, it just > applies your settings in this area, whose defaults have not changed > of recent, as far as I recall. Finally, the "change" was not > brought about by Org, but by Emacs. Org just (belatedly) tagged > along. Best regards, Gustavo. For me is now better to simple adjust: org-indent-region variable just as you said. Thank you for references.