From mboxrd@z Thu Jan 1 00:00:00 1970 From: Detlef Steuer Subject: Re: Survey: changing a few default settings for Org 9.4 Date: Wed, 19 Feb 2020 17:50:52 +0100 Message-ID: <20200219175052.54499e22@gaia> References: <87pnebf2ku.fsf@gnu.org> <87blpu37q6.fsf@fastmail.fm> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Return-path: Received: from eggs.gnu.org ([2001:470:142:3::10]:43572) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1j4SYt-0002K1-Nq for emacs-orgmode@gnu.org; Wed, 19 Feb 2020 11:51:00 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1j4SYs-0006nW-Et for emacs-orgmode@gnu.org; Wed, 19 Feb 2020 11:50:59 -0500 Received: from mail-sender-5.unibw-hamburg.de ([139.11.10.105]:61670 helo=premail.unibw-hamburg.de) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1j4SYs-0006n8-7p for emacs-orgmode@gnu.org; Wed, 19 Feb 2020 11:50:58 -0500 Received: from rzav4.unibw-hamburg.de ([139.11.12.54]:7361) by premail.unibw-hamburg.de with esmtp (HSU Mailserver) (envelope-from ) id 1j4SYq-00069K-Nn for emacs-orgmode@gnu.org; Wed, 19 Feb 2020 17:50:56 +0100 In-Reply-To: <87blpu37q6.fsf@fastmail.fm> List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane-mx.org@gnu.org Sender: "Emacs-orgmode" To: emacs-orgmode@gnu.org Am Wed, 19 Feb 2020 09:41:21 -0600 schrieb Matthew Lundin : > Bastien writes: > > > - org-fontify-done-headline => t > > > > This is useful to visualize done headlines and can be easily > > turned off, while not being easily discovered for Org newcomers. > > I find this a bit visually distracting, but that's likely because I've > used Org mode in the "old school" way for so long. So no strong > opinions on this one. Same here. No strong opinion. > > > - org-hide-emphasis-markers => t > > - org-hide-macro-markers => t > > > > The two changes proposed above will probably trigger some > > reactions as they touch something very sensitive: whether Org > > should try to be "too clever" at making things invisible. I am all > > for letting Org newcomers enjoying these visual enhancements, while > > letting experts turning them off if needed. > > I have a few concerns about this. I believe that markup syntax, as a > rule, should be visible. Most markdown editors do not hide markup by > default. I realize that there are some exceptions in Org (e.g., > links). But editing around the invisible boundaries of links can be > in Org can be fussy (sometimes I have to do M-x visible-mode when > editing near the edges of links). So I'd recommend not changing the > default here, especially for emphasis markers. > I really dislike invisible markup as default. Org is a markup "language", not a word-processor. Even links feel more consistent when visible. So fully agree with Matt again. > > - org-allow-promoting-top-level-subtree => t > > > > With the current default of nil, an error is thrown when the user > > tries to promote a top level subtree. The new default setting > > would let users convert the top level heading to a commented > > heading. > > From my point of view, this is too destructive a default. I think it > makes it too easy accidentally to turn important TODO headlines into > commented lines (which will be buried in another entry). If I wanted > to change a first level headline to a comment, it would only take two > keystrokes (C-d #). Forcing users to type this explicitly seems > preferable to creating a risk that users will accidentally bury/lose > first-level headlines as comments in another entry. And again a simple +1. Detlef > > Matt >