emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Tim Cross <theophilusx@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: Changed list indentation behavior: how to revert?
Date: Mon, 16 Nov 2020 18:12:35 +1100	[thread overview]
Message-ID: <874klpbwrg.fsf@gmail.com> (raw)
In-Reply-To: <737364.1605509661@apollo2.minshall.org>


Greg Minshall <minshall@umich.edu> writes:

> i wonder if a grid might help?  i.e., contexts in which we are all
> happy, others where we might disagree?  below, i try; i'm sure i've
> missed cases.
>
> question: what does <RET> do/would we like it to do when we are in?
>
> =========================================
> tables: next row, current column
>
> Org Src buffers: electric-indent per declared language major
> mode rules.
>
> src blocks: same as in Org Src buffers (i think there have been some
> very nice "recent" improvements here, which are great, and for which,
> belated thanks!)
>
> ^^   i think we are all happy with those
> =========================================
> =========================================
> vv   here, i think, well, "Houston, ..." :)
>
> after n* heading:
>     column 1
>   vs
>     column n+2
>
> list entry (end of line):
>     column where previous "-" was (to start a new list item)
>   vs
>     two columns *after* where previous "-" was (to continue with the
>     current list item)
>
> immediately after (non-blank, non-list, non-heading) with text starting
> in column n:
>     column 1
>   vs
>     column n
>
> immediately after a blank line:
>     column 1
>   vs
>     column of first non-blank character of most recent non-blank line?
> =========================================
>
> surveymonkey, anyone?  :)  not to vote, but i'm curious to what extent
> we divide cleanly into two groups (in which case, maybe an option for
> which "major mode indentation" style one prefers for org-mode makes
> sense), or if we are uniformly distributed across the power set. :)
>
> btw, it seems to me that M-q (fill-paragraph) also has *something* to
> say here.  i.e., though *i* want <RET> from a list entry to line me up
> at the previous "-", i want M-q within a list entry to add new lines
> starting two columns past that point.  i guess i see it as orthogonal
> (and, so far, non-controversial) to the current discussion, and hope it
> so stays!
>
> cheers, Greg

Hi Greg,

I think there are more than two groups.

I would start by considering it as two top level groups

  1. Indentation behaviour with electric-indent enabled and
  org-adapt-indent set to t (the current defaults)
  2. Indentation behaviour with electric-indent disabled as suggested in
  the org NEWS file.
  3. Indentation behaviour with different values for org-adaptive-indentation.

Then we have the different values which org-adapt-indentation can be set
to that will 'tweak' the way adaptive indentation works in different
contexts.

It is my guess that the majority of people can in fact have the
behaviour they want either by turning of electric indent mode or by
setting org-adaptive-indentation to one of the supported values. I would
encourage anyone who is not happy with the default to look at the
different supported values for org-adaptive-indentation to see if the
tweaking it provides might make org indentation work closer to what they
like (as opposed to turning all automatic indentation off).

There are probably a few edge cases, but to identify those, we need to
first eliminate all the cases which can be 'resolved' with existing
configuration options.

Tim

--
Tim Cross


  reply	other threads:[~2020-11-16  7:13 UTC|newest]

Thread overview: 76+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-13 17:30 Changed list indentation behavior: how to revert? Karl Voit
2020-11-13 21:10 ` Gustavo Barros
2020-11-13 21:38   ` Jean Louis
2020-11-14  3:02     ` Greg Minshall
2020-11-13 21:47   ` Jean Louis
2020-11-13 22:13     ` Gustavo Barros
2020-11-13 22:21       ` Jean Louis
2020-11-14 17:28         ` Diego Zamboni
2020-11-14 19:10           ` Jean Louis
2020-11-15 12:44             ` Kévin Le Gouguec
2020-11-15 13:26               ` Jean Louis
2020-11-15 21:59                 ` Kévin Le Gouguec
2020-11-15 22:15                   ` Jean Louis
2020-11-16  7:15                   ` Dr. Arne Babenhauserheide
2020-11-16  6:26               ` Greg Minshall
2020-11-14 10:45   ` Diego Zamboni
2020-11-13 21:31 ` Jean Louis
2020-11-14 22:43 ` David Rogers
2020-11-15  5:38   ` Jean Louis
2020-11-15  7:47     ` David Rogers
2020-11-15  8:54       ` Jean Louis
2020-11-15 10:37       ` Greg Minshall
2020-11-15 11:42         ` Tim Cross
2020-11-15 11:48         ` Gustavo Barros
2020-11-15 11:58           ` Detlef Steuer
2020-11-15 12:09           ` Jean Louis
2020-11-15 14:50             ` Gustavo Barros
2020-11-15 15:11               ` Jean Louis
2020-11-15 10:44       ` Dr. Arne Babenhauserheide
2020-11-15 11:22         ` Detlef Steuer
2020-11-15 14:03           ` Kévin Le Gouguec
2020-11-16  5:24             ` Kyle Meyer
2020-11-16  6:41               ` Tim Cross
2020-11-16  7:15                 ` Tim Cross
2020-11-16 11:21                   ` Gustavo Barros
2020-11-16 23:24                     ` T.F. Torrey
2020-11-17  1:21                       ` Tom Gillespie
2020-11-17  7:01                         ` Dr. Arne Babenhauserheide
2020-11-17  7:48                       ` Michal Politowski
2020-11-19  4:17                     ` Marcel Ventosa
2020-11-16  8:06                 ` Kévin Le Gouguec
2020-11-16 12:10                 ` Bill Burdick
2020-11-16  6:54               ` Greg Minshall
2020-11-16  7:12                 ` Tim Cross [this message]
2020-11-17  4:03                   ` Greg Minshall
2020-11-17  5:25                     ` Tim Cross
2020-11-17 13:15                       ` Greg Minshall
2020-11-16  7:01               ` Dr. Arne Babenhauserheide
2020-11-16  7:22                 ` Tim Cross
2020-11-16 16:04                   ` Dr. Arne Babenhauserheide
2020-11-16 16:26                     ` Tom Gillespie
2020-11-16 18:12                       ` gyro funch
2020-11-16 18:48                         ` Tom Gillespie
2020-11-16 19:41                           ` Bill Burdick
2020-11-16 19:56                             ` Tom Gillespie
2020-11-16 21:50                             ` Tim Cross
2020-11-16 23:01                               ` Tom Gillespie
2020-11-16 21:44                           ` Tim Cross
2020-11-16 18:20                       ` gyro funch
2020-11-16 20:56                       ` Tim Cross
2020-11-16 21:35                         ` Bill Burdick
2020-11-16 22:44                         ` Tom Gillespie
2020-11-16 23:55                         ` Dr. Arne Babenhauserheide
2020-11-17  9:05                           ` Stefan Nobis
2020-11-17  9:15                             ` Loris Bennett
2020-11-17  9:32                             ` Diego Zamboni
2020-11-17 14:29                             ` Dr. Arne Babenhauserheide
2020-11-17 16:25                               ` Robert Pluim
2020-11-16 23:39                       ` Dr. Arne Babenhauserheide
2020-11-16 21:35                     ` Tim Cross
2020-11-17  0:11                       ` Dr. Arne Babenhauserheide
2020-11-17  8:45                         ` Detlef Steuer
2020-11-17  9:41                           ` Jean Louis
2020-11-17 15:33                     ` Maxim Nikulin
2020-11-16 13:00                 ` Uwe Brauer
2020-11-16 16:10                   ` Dr. Arne Babenhauserheide

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=874klpbwrg.fsf@gmail.com \
    --to=theophilusx@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).