[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Changed list indentation behavior: how to revert?
From: |
Kévin Le Gouguec |
Subject: |
Re: Changed list indentation behavior: how to revert? |
Date: |
Sun, 15 Nov 2020 22:59:43 +0100 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/28.0.50 (gnu/linux) |
Jean Louis <bugs@gnu.support> writes:
> There is just slight difference, and that is what I learned from
> introduction to Org mode that it is "plain text" kind of mode. I can
> do and write how I wish. My habit comes from being used to indent when
> I want and then to follow indentation in that specific paragraph. That
> is really great.
>
> But I was not used to have it indented by programmer like the
> introduction of this new default feature, which I consider is not
> useful to be default.
Note that even before this change, Org's indentation already behaved
like a "programming mode". TAB does not allow you to move to "any
column":
- either org-adapt-indentation is t (the default) and TAB moves your
paragraph to column LEVEL+1,
- or it is nil, and TAB is a no-op.
> Observe this official presentation and you will see how current
> indentation is not consistent to what is shown:
> https://orgmode.org/resources/img/features/folding.gif
>
> Look at this official presentation and you will see that even headings
> are indented for which we say it should not be so:
> https://orgmode.org/resources/img/features/clocking.svg
Yep, AFAICT this has been produced with org-indent-mode, which
soft-indents using overlays.
> The official presentation here:
> https://orgmode.org/
>
> does not show any indentation at all.
>
> And in Info file I find nothing of it.
Yep; what this (along with the way org-adapt-indentation is unset in
Org's own repo) suggests to me is that Org, by default, should not
indent section bodies.
This means *not only* that RET should not indent, but that /TAB/ should
not rigidly indent to column LEVEL+1 (I don't have a strong opinion
about whether it should rigidly indent to column 0, or if it should
behave as in text-mode).
So AFAIU the issue lies not with RET becoming consistent with the rest
of Emacs and doing "insert newline then indent smartly"; rather it lies
with how Org defines "smartly". From what I gather from this thread,
lots of folks would like Org to keep section bodies at column 0.
> All I say, when default is introduced, should be well documented how
> and why. Before it is introduced it is better to discuss wider with
> people.
>
> Few of people reading these exchanges may find how to turn it off,
> majority will not find it.
Before being applied, this change has been discussed on emacs-devel and
emacs-orgmode; it has then been documented in ORG-NEWS. Which other
places do you think we should have reached out to?
>> IIUC this can be toggled off by setting org-adapt-indentation to nil;
>> FWIW this is what the .dir-locals.el file at the root of Org's
>> repository doe
>
> With 2000+ directories containing Org file of persons, held on this
> system that would mean turning it on 2000+ times. Because in general I
> do not use that type of indentation I have just set it in main
> ~/.emacs.d/init.el file.
>
> We concluded that configuring is easy and that is great.
>
> What is not concluded is that the default impacts too many people who
> may not find out how to configure it back and that designing user
> interface shall be made with more care.
I admit to not having put as much thought in a "migration plan" as I
could have. My reasoning was that since Org indents text by default
(/when/ hitting TAB or using the "smart newline" command), users were
probably fine with it.
IIUC I failed to understand that:
- Plenty of Org users do not expect it to behave like programming modes
wrt indentation (they might not even use programming modes).
- These users were using RET as a "dumb newline" command, unaware
that by default, Org considers that text should be indented.
- org-adapt-indentation…
- exists (really, I just found out about it today, after wondering
why on Earth Org does not indent text in doc/org-guide.org, and
tracing it to the repository's directory-local variables).
- has a default value that does not reflect how Org text is indented
in official examples, nor in Org's own repository.
- Re: Changed list indentation behavior: how to revert?, (continued)
- Re: Changed list indentation behavior: how to revert?, Gustavo Barros, 2020/11/13
- Re: Changed list indentation behavior: how to revert?, Jean Louis, 2020/11/13
- Re: Changed list indentation behavior: how to revert?, Jean Louis, 2020/11/13
- Re: Changed list indentation behavior: how to revert?, Gustavo Barros, 2020/11/13
- Re: Changed list indentation behavior: how to revert?, Jean Louis, 2020/11/14
- Re: Changed list indentation behavior: how to revert?, Diego Zamboni, 2020/11/14
- Re: Changed list indentation behavior: how to revert?, Jean Louis, 2020/11/14
- Re: Changed list indentation behavior: how to revert?, Kévin Le Gouguec, 2020/11/15
- Re: Changed list indentation behavior: how to revert?, Jean Louis, 2020/11/15
- Re: Changed list indentation behavior: how to revert?,
Kévin Le Gouguec <=
- Re: Changed list indentation behavior: how to revert?, Jean Louis, 2020/11/15
- Re: Changed list indentation behavior: how to revert?, Dr. Arne Babenhauserheide, 2020/11/16
- Re: Changed list indentation behavior: how to revert?, Greg Minshall, 2020/11/16
Re: Changed list indentation behavior: how to revert?, Diego Zamboni, 2020/11/14
Re: Changed list indentation behavior: how to revert?, Jean Louis, 2020/11/13
Re: Changed list indentation behavior: how to revert?, David Rogers, 2020/11/14