emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Kévin Le Gouguec" <kevin.legouguec@gmail.com>
To: James Powell <powellj@pdx.edu>
Cc: 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 13:25:35 +0200	[thread overview]
Message-ID: <87v97qq18w.fsf@gmail.com> (raw)
In-Reply-To: <874kfazzle.fsf@nicolasgoaziou.fr> (Nicolas Goaziou's message of "Mon, 10 May 2021 11:51:09 +0200")

Nicolas Goaziou <mail@nicolasgoaziou.fr> writes:

>> Note also that "- a<smart newline><smart newline><smart newline>" goes
>> back to column 0.  (FWIW I think that's a bit unwieldy; going back to
>> column 0 on the /second/ <smart newline> would make more sense to me, as
>> it would correspond to a "paragraph break")
> It would make it painful to insert a blank line within a list item.
> OTOH, on the third newline, you are really out of the list. 

Fair enough!  I figured the current behaviour made it easier to write
"multiple paragraphs" in a single list item, but I was unsure if anyone
actually relied on that.  Thanks for confirming this hunch :)

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.

  reply	other threads:[~2021-05-10 11:26 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 [this message]
2021-05-10 12:36       ` Greg Minshall
2021-05-10 13:08         ` Kévin Le Gouguec
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=87v97qq18w.fsf@gmail.com \
    --to=kevin.legouguec@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --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).