From: Max Nikulin <manikulin@gmail.com>
To: 51167@debbugs.gnu.org
Subject: bug#51167: 29.0.50; org-indent-line broken
Date: Sun, 17 Oct 2021 22:19:59 +0700 [thread overview]
Message-ID: <32780b45-d020-d3f0-85dd-7592401697cf@gmail.com> (raw)
In-Reply-To: <3aff866c-61d1-602b-5468-6026c251a0c5@easy-emacs.de>
close 51167
quit
On 17/10/2021 03:02, Andreas Röhler wrote:
> On 13.10.21 14:59, Max Nikulin wrote:
>> On 13/10/2021 01:35, Kévin Le Gouguec wrote:
>>> Andreas Röhler writes:
>>>
>>>> With following stuff in org-mode buffer:
>>>>
>>>> * bla
>>>> asd
>>>>
>>>> M-x org-indent-line RET on second line has no effect.
>>
>> Andreas, do the following settings make behavior consistent with you
>> expectations?
>>
>> (add-hook 'org-mode-hook (lambda () (electric-indent-local-mode -1)))
>> (setq org-adapt-indentation t)
>
> Thanks. That works for me.
So it is not a bug.
> Still thinking a command "indent" should indent.
Such settings are not the best choice for defaults. They are not friendly to
- New users who do not press TAB after each RET, so they later get
inconsistent indentation after promoting/demoting/refiling headings.
- Users who write long documents where convenience of indented
paragraphs is disputed. Likely org-indent is better to get visual indent
without adding spaces in front of every line
- VCS because of promoting or demoting headings results in overblown
patches.
I do not think that behavior of TAB in Org is deviates from major modes.
(Side note: sometimes I do not mind to have indent accordingly to my
taste even if it is not conventional one for particular structure.)
prev parent reply other threads:[~2021-10-17 15:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <541af1a2-d532-13f7-8cf6-6edbfe64fdc1@easy-emacs.de>
2021-10-12 18:35 ` bug#51167: 29.0.50; org-indent-line broken Kévin Le Gouguec
2021-10-13 6:47 ` Andreas Röhler
2021-10-13 7:34 ` Kévin Le Gouguec
2021-10-13 7:48 ` Andreas Röhler
2021-10-13 9:01 ` Kévin Le Gouguec
2021-10-13 12:59 ` Max Nikulin
2021-10-16 20:02 ` Andreas Röhler
2021-10-17 15:19 ` Max Nikulin [this message]
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=32780b45-d020-d3f0-85dd-7592401697cf@gmail.com \
--to=manikulin@gmail.com \
--cc=51167@debbugs.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).