From: Carsten Dominik <carsten.dominik@gmail.com>
To: Ihor Radchenko <yantar92@posteo.net>
Cc: Matt <matt@excalamus.com>,
"Sławomir Grochowski" <slawomir.grochowski@gmail.com>,
emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: [PATCH] doc/org-manual.org (Checkboxes): move section 'Checkboxes' from 'TODO Items' to 'Plain Lists'
Date: Tue, 20 Aug 2024 12:45:30 +0200 [thread overview]
Message-ID: <CADn3Z2JLAWvK883yiV_Lx=nYyKrL6mao5v1wUp3u9mJZJgwC8g@mail.gmail.com> (raw)
In-Reply-To: <87o7bw6by2.fsf@localhost>
[-- Attachment #1: Type: text/plain, Size: 3690 bytes --]
On Sat, Mar 2, 2024 at 1:40 PM Ihor Radchenko <yantar92@posteo.net> wrote:
> Matt <matt@excalamus.com> writes:
>
> > >...or did you not provided arguments /why/ the
> > > section should be moved? I need to understand what kind of improvement
> > > it would provide to the manual.
> >
> > I didn't know that's what you were looking for. When I said, "I had
> responded in favor..." it was in response to your prior message which said,
>
> Let me clarify.
> I am personally neutral about where the concept of checkboxes is
> introduced. Either way is generally possible.
>
> However, moving "Checkboxes" section will require some work. We will
> need to make sure that the overall flow of the manual is _improved_.
> The question is how to judge "improved".
>
> From my point of view, the manual will be improved by the proposed
> change if (a) we can see clear logical argument why the proposed
> rearrangement is superior; or/and (b) *a number* of Org users /feel/ that
> the rearrangement will improve thins.
>
> Your response is in favor, but you did not appear to present logical
> arguments. So, I classify your response as if you /feel/ that the
> rearrangement will be better. Such response of a single person is not
> very convincing. I'd only see rearrangement justified if many users are
> in favor.
>
> Another question is when there is a clear logical argument. Such
> argument would not require multiple users to agree as it would stand by
> its own.
>
> >> No comments arrived within one month.
> >
> > This is incorrect albeit understandable. I had responded and,
> therefore, there were not "no comments." However, it looks like I
> responded in the wrong thread! ("Re: [PATCH] doc/org-manual.org:
> Checkboxes, add checkbox states examples") That's my bad!
>
> I indeed missed your comment when writing this particular sentence.
>
> > Regarding reasoning, I'm in favor of the move for the reasons Sławomir
> gave:
> >
> >> Because checkbox can only exist in a plain list, as a plain list
> feature.
> >> So the section should be under 'Plain Lists' heading not under 'TODO
> Items'.
> >
> > The issue is checkbox usage is split between different sections of the
> manual.
> >
> > You had responded to this by saying,
> >
> >> Both arrangements are logical. Checkboxes are useful as a complement to
> >> TODO items. And they are also indeed a plain list feature.
> >
> > It seems we're all agreed the proposed arrangement is logical and that
> the issue is valid. I don't think it needs extra justification.
>
> Yes, the proposed arrangement is logical. So is the existing
> arrangement. The problem is that I do not see why the proposed
> arrangement is *better*.
>
> > Conceding this point, which we all appear to, the issue becomes which
> arrangement we should use?
> >
> > Originally, we were reluctant to move the Checkboxes section only
> because Carston had moved it previously. Unfortunately, we don't know
> *why* Carston moved it. This isn't a very contestable justification.
>
Checkboxes are meta data that is related to actions. Introducing checkboxes
in the "Structure -> Plain lists" section would be similar to introducing
TODO keywords in the "Headlines" section. Like you, I can find arguments
for both arrangements - but this was the reasoning I used when I structured
the manual.
- Carsten
>
> I agree.
>
> --
> Ihor Radchenko // yantar92,
> Org mode contributor,
> Learn more about Org mode at <https://orgmode.org/>.
> Support Org development at <https://liberapay.com/org-mode>,
> or support my work at <https://liberapay.com/yantar92>
>
>
[-- Attachment #2: Type: text/html, Size: 4892 bytes --]
prev parent reply other threads:[~2024-08-20 10:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-25 13:05 [PATCH] doc/org-manual.org (Checkboxes): move section 'Checkboxes' from 'TODO Items' to 'Plain Lists' Sławomir Grochowski
2024-01-25 22:36 ` Ihor Radchenko
2024-02-26 8:59 ` Ihor Radchenko
2024-02-27 16:47 ` Matt
2024-02-27 23:07 ` Sławomir Grochowski
2024-02-28 12:20 ` Ihor Radchenko
2024-02-28 19:10 ` Matt
2024-03-02 12:43 ` Ihor Radchenko
2024-08-20 10:45 ` Carsten Dominik [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='CADn3Z2JLAWvK883yiV_Lx=nYyKrL6mao5v1wUp3u9mJZJgwC8g@mail.gmail.com' \
--to=carsten.dominik@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=matt@excalamus.com \
--cc=slawomir.grochowski@gmail.com \
--cc=yantar92@posteo.net \
/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).