emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Texas Cyberthal <texas.cyberthal@gmail.com>
To: "emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>
Subject: Re: org-adaptive-indent nil default
Date: Sat, 8 Feb 2020 17:19:43 +0800	[thread overview]
Message-ID: <CAMUm49252qD+wJ95FxdEy1TqZMOC6C3RC+TPcUuWRUsLcdst8g@mail.gmail.com> (raw)

#+begin_quote alphapapa
I think you have a better case for changing this setting.  However, I
think there is another consideration: the default settings do not put
blank lines between headings and their entry text, and without any
indentation, headings and entry text on varying levels tends to blend
together, making for very poor readability.  Disabling this setting
would make this problem worse.
#+end_quote

I see what you mean now. Spacemacs lacks this problem thanks to org-bullets.

> the default settings do not put blank lines between headings and their entry text,

It doesn't. However, it puts a blank line between entry text and the
next heading, when the current heading has a blank line preceding it.

I always took this as advice to separate entry text and headings with
blank lines. I assumed the lack of an automatic blank line immediately
after a heading was due to the fact that one might wish to place a
heading or a drawer on that line.

I see that under the vanilla defaults, with no blank lines, the little
adaptive indent at the start of the wrapped entry text helps one spot
the start of a heading's *****

This is no big deal. Indenting the first line of a paragraph is a
matter of taste. I had it confused with org-indent-mode, which wastes
tons of space, but isn't enabled by default.

Anyway, vanilla Org has profound UI issues that can't be sufficiently
addressed to give normie-noobs a competitive modern induction
experience. So it may as well stay however makes the devs happiest.

                 reply	other threads:[~2020-02-08  9:20 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=CAMUm49252qD+wJ95FxdEy1TqZMOC6C3RC+TPcUuWRUsLcdst8g@mail.gmail.com \
    --to=texas.cyberthal@gmail.com \
    --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).