emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Kévin Le Gouguec" <kevin.legouguec@gmail.com>
To: Greg Minshall <minshall@umich.edu>
Cc: James Powell <powellj@pdx.edu>, emacs-orgmode@gnu.org
Subject: Re: Bug: spurious change in list indent cursor motion [9.4.4 (9.4.4-dist @ /home/powellj/elisp/org-9.4.4/lisp/)]
Date: Mon, 10 May 2021 15:08:57 +0200	[thread overview]
Message-ID: <87r1iepwgm.fsf@gmail.com> (raw)
In-Reply-To: <1198610.1620650198@apollo2.minshall.org> (Greg Minshall's message of "Mon, 10 May 2021 15:36:38 +0300")

Greg Minshall <minshall@umich.edu> writes:

> Kevin,
>> FWIW, during the latest poll somebody suggested making org-indent-line
>> cycle through "syntactically valid" indentation levels when hitting TAB
>> repeatedly, like python-indent-line-function; I like this idea.
> i think (*) the current "master" branch allows you to type "-
> fu<RET>-<TAB> *bar" (where the " *" bit means "zero or more spaces").
> but, i guess because of folding, it's that sensitive, doesn't cycle when
> any non-blank is typed.

Right, that allows changing the indentation level of a newly inserted
bullet point; my remark was about changing the indentation level of
regular text, e.g. "- list item<RET><TAB>unindented paragraph".

C-j works well enough when there are only two valid positions (column 2
and column 0); in this situation though:

- foo
  - bar
  - baz<point>
It would be nice if RET TAB TAB TAB… cycled between columns 2→0→4…, just
like M-RET TAB TAB TAB… cycles between columns 6→2→4…

  reply	other threads:[~2021-05-10 13:09 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-09 21:17 Bug: spurious change in list indent cursor motion [9.4.4 (9.4.4-dist @ /home/powellj/elisp/org-9.4.4/lisp/)] James Powell
2021-05-09 21:58 ` Kévin Le Gouguec
2021-05-10  9:51   ` Nicolas Goaziou
2021-05-10 11:25     ` Kévin Le Gouguec
2021-05-10 12:36       ` Greg Minshall
2021-05-10 13:08         ` Kévin Le Gouguec [this message]
2021-05-10 14:50           ` Greg Minshall

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:

  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=87r1iepwgm.fsf@gmail.com \
    --to=kevin.legouguec@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=minshall@umich.edu \
    --cc=powellj@pdx.edu \


* 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


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