all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: abq@bitrot.link
To: Ihor Radchenko <yantar92@posteo.net>
Cc: emacs-orgmode@gnu.org
Subject: Re: Is the cascading logic of outlines a feature, or a design bug?
Date: Mon, 26 Dec 2022 17:23:45 +0000	[thread overview]
Message-ID: <a923d5378641a7c0c2b94ff103ba5ebf@bitrot.link> (raw)
In-Reply-To: <87cz86qxrc.fsf@localhost>

On 2022-12-26 10:12, Ihor Radchenko wrote:
> It is not a bug. It is not a feature. Just a design decision. With pros
> and cons. Doing the opposite would also have pros and cons.
> 
> I suggest you to elaborate about what exact properties of outlines you
> are missing.

OK, a design tradeoff was made, with a cost and a benefit.

The cost was the restriction at hand. Its mention in the FAQ is 
indication that it does actually affect people. Tomas also just replied 
that it's sometimes an obstacle for him, which he needs to work around.

So, that addresses the cost. What was the benefit?


  reply	other threads:[~2022-12-26 17:24 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-26  6:47 Is the cascading logic of outlines a feature, or a design bug? abq
2022-12-26  7:51 ` tomas
2022-12-26 10:12 ` Ihor Radchenko
2022-12-26 17:23   ` abq [this message]
2022-12-26 17:32     ` tomas
2022-12-26 17:36     ` Ihor Radchenko
2022-12-26 18:37       ` tomas
2022-12-27  7:21         ` Marcin Borkowski
2022-12-27  9:00           ` tomas
2022-12-28  6:40             ` Marcin Borkowski
2022-12-28  7:28               ` Heinz Tuechler
2022-12-28  9:29                 ` tomas
2022-12-26 12:38 ` Max Nikulin
2022-12-26 17:03   ` abq
2022-12-27 16:02     ` Max Nikulin
2022-12-28  1:52       ` Samuel Wales
2022-12-28  7:14 ` Stefan Nobis
2022-12-28  7:21   ` Samuel Wales
2022-12-28  8:45   ` Greg Minshall
2022-12-28  9:13     ` Ihor Radchenko
2022-12-28  9:34       ` Greg Minshall
2022-12-28  9:34   ` tomas

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=a923d5378641a7c0c2b94ff103ba5ebf@bitrot.link \
    --to=abq@bitrot.link \
    --cc=emacs-orgmode@gnu.org \
    --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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.