emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Samuel Wales <samologist@gmail.com>
To: Bastien <bzg@gnu.org>
Cc: Adam Porter <adam@alphapapa.net>, emacs-orgmode@gnu.org
Subject: Re: org-adapt-indentation default should be nil [legibility 3/6]
Date: Mon, 10 Feb 2020 13:33:59 -0700	[thread overview]
Message-ID: <CAJcAo8sF9ts2Vq71f3jbiefOZcz6fXabDQREwXuRm2F=-fy8YA@mail.gmail.com> (raw)
In-Reply-To: <87wo8uapmk.fsf@gnu.org>

[this is addressed to bastien]

hi,

if you are thinking of changing the default to indenting meta lines
and asking for opinions on that:

fwiw, if org /were starting out/, i would propose that meta stuff not
be indented at all either.  then the regexps everywhere could be
reliable.  and it reduces number of things to think about.  keyboard
macros, grep, third party tools in and outside of emacs.

the idea being keep to the basics so there will be no surprises.

i have a case i won't go into where a tool cannot reliably parse such
lines, because it has to distinguish semantic indentation and physical
aesthetic indentation.  this can't be done without ai in its context.
so the tool /outlaws/ physical indentation for a feature.

it doesn't actually shoot you or post wanted signs if you physically
indent, but the feature will not work.

imo there are more arguments too.

for example, state change lines and notes can be wide.  for
accessibility, i always want the default to be the one that does not
affect whose who need it, who already have too much to deal with.
this is my opinion.

obviously, as a default not indenting text as you seem to propose is
good for newcomers.

as for org as it is now, with a mixture of at least 3 indentation
styles in the wild, idk.

fwiw.

  reply	other threads:[~2020-02-10 20:34 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-04  4:09 org-adapt-indentation default should be nil [legibility 3/6] Texas Cyberthal
2020-02-04  7:21 ` Adam Porter
2020-02-10  7:05   ` Bastien
2020-02-10 20:33     ` Samuel Wales [this message]
2020-02-10 21:52       ` Bastien
2020-02-10 22:01         ` Samuel Wales
  -- strict thread matches above, loose matches on Subject: below --
2020-02-04 22:00 Texas Cyberthal
2020-02-05 16:12 ` Adam Porter

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='CAJcAo8sF9ts2Vq71f3jbiefOZcz6fXabDQREwXuRm2F=-fy8YA@mail.gmail.com' \
    --to=samologist@gmail.com \
    --cc=adam@alphapapa.net \
    --cc=bzg@gnu.org \
    --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).