emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Max Nikulin <manikulin@gmail.com>
To: abq@bitrot.link
Cc: emacs-orgmode@gnu.org
Subject: Re: Is the cascading logic of outlines a feature, or a design bug?
Date: Tue, 27 Dec 2022 23:02:12 +0700	[thread overview]
Message-ID: <ccfcdae9-f071-681a-3495-31d13be2778d@gmail.com> (raw)
In-Reply-To: <d8b7db17036ed610031a3c25b48258d6@bitrot.link>

On 27/12/2022 00:03, abq@bitrot.link wrote:
> When I searched prior to posting, the only info I could find was how to 
> work around the restriction. But my question isn't how to work around 
> it; my question is, what is its purpose?

I have an impression that I saw messages explaining that the real 
problem is to implement the feature consistently and to avoid too much 
code for handling it in various functions. I do not have specific links. 
Reading such discussion I would pay more attention to messages from 
Carsten, Bastien, Nicolas.

> It doesn't affect regexp search efficiency.

Regexps would be more complex, sometimes several iterations would be 
required. You may underestimate amount of code that should be adapted 
for this feature.

In general, I do not mind to have such feature e.g. to have an overview 
headings with comments between deep dive notes. However if I desperately 
need it, I will write a custom unfolding function (for tagged 
subheadings or for drawers). I am unsure that benefits outweigh 
additional complexity and performance penalty.

This topic belongs to a several feature requests that pop up regularly 
and fade with almost no outcome (intra-word emphasis, merged cells in 
tables).


  reply	other threads:[~2022-12-27 16:03 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
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 [this message]
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

  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=ccfcdae9-f071-681a-3495-31d13be2778d@gmail.com \
    --to=manikulin@gmail.com \
    --cc=abq@bitrot.link \
    --cc=emacs-orgmode@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).