emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Detlef Steuer <steuer@hsu-hh.de>
To: emacs-orgmode@gnu.org
Subject: Re: Survey: changing a few default settings for Org 9.4
Date: Wed, 19 Feb 2020 17:50:52 +0100	[thread overview]
Message-ID: <20200219175052.54499e22@gaia> (raw)
In-Reply-To: <87blpu37q6.fsf@fastmail.fm>

Am Wed, 19 Feb 2020 09:41:21 -0600
schrieb Matthew Lundin <mdl@imapmail.org>:

> Bastien <bzg@gnu.org> 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
> 

  parent reply	other threads:[~2020-02-19 16:51 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-19  7:39 Survey: changing a few default settings for Org 9.4 Bastien
2020-02-19  8:57 ` Samuel Wales
2020-02-19  9:01   ` Bastien
2020-02-19 20:02   ` Samuel Wales
2020-02-19 20:15     ` Marcin Borkowski
2020-02-19 21:35       ` Bastien
2020-02-19 22:06         ` Samuel Wales
2020-02-19 11:03 ` Marco Wahl
2020-02-19 11:41   ` Bastien
2020-02-19 13:21     ` Marco Wahl
2020-02-19 13:39       ` Bastien
2020-02-19 17:57         ` Marco Wahl
2020-02-19 20:44           ` Bastien
2020-02-20  4:11       ` Adam Porter
2020-02-19 11:30 ` Nicolas Goaziou
2020-02-19 11:57   ` Bastien
2020-02-19 14:07     ` Nicolas Goaziou
2020-02-19 17:24       ` Bastien
2020-02-19 23:23         ` Vladimir Lomov
2020-02-19 23:53           ` Bastien
2020-02-20  0:20             ` Samuel Wales
2020-02-19 12:58   ` Tim Cross
2020-02-19 13:22     ` Bastien
2020-02-19 15:06       ` Tim Cross
2020-02-19 13:03   ` AW
2020-02-19 15:41 ` Matthew Lundin
2020-02-19 16:16   ` Joost Kremers
2020-02-19 17:13     ` Bastien
2020-02-19 16:50   ` Detlef Steuer [this message]
2020-02-19 17:14     ` Bastien
2020-02-20  4:07 ` Adam Porter
2020-02-20  7:10   ` Bastien
2020-02-20 14:10     ` Kaushal Modi
2020-02-21 15:49 ` Bastien
2020-02-21 19:36   ` Diego Zamboni
2020-02-21 21:28     ` Archenoth
2020-02-22  9:38       ` Bastien
2020-02-22 12:45         ` Nicolas Goaziou
2020-02-22 13:31           ` Bastien
2020-02-22 18:57           ` Archenoth
2020-03-18  2:20 ` Mark E. Shoulson
2020-03-18  8:58   ` Norman Tovey-Walsh
2020-03-18 20:47     ` Hiding emphasis markers Mark E. Shoulson
2020-05-22 16:47       ` Bastien

Reply instructions:

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:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20200219175052.54499e22@gaia \
    --to=steuer@hsu-hh.de \
    --cc=emacs-orgmode@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* 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

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

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).