emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed

From: Corwin Brust <corwin@bru.st>
To: Adam Porter <adam@alphapapa.net>
Cc: emacs-orgmode@gnu.org
Subject: Re: Provide org-insert-subitem
Date: Wed, 12 Feb 2020 23:13:21 -0600	[thread overview]
Message-ID: <CAJf-WoS=O5WVggB7XavBv_FaeVjrNSQauCcOVBE9v3DiKTc==w@mail.gmail.com> (raw)
In-Reply-To: <87sgjflclf.fsf@alphapapa.net>

[-- Attachment #1: Type: text/plain, Size: 1121 bytes --]

Hi,

On Wed, Feb 12, 2020, 15:28 Adam Porter <adam@alphapapa.net> wrote:

> Hi Bastien,
>
> Bastien <bzg@gnu.org> writes:
>
> > I still find it strange to keep functions that are used nowhere in the
> > Org's core--except of course for functions that explicitely mention as
> > usable by the user (e.g. `org-clock-persistence-insinuate'.)
>

[snip]

And it's in org.el, so it's in Org's
> "core", right?  I guess we're thinking in different terms.
>
> Inserting a subheading or subitem is a very common operation in an
> outlining and list-making tool, so it would seem like a significant
> regression to remove it.
>

I think there's an implied -and usually misleading‐ correlation between the
importance of a function and the count of self-references -meaning uses in
the defining package- shown from help buffers.    It would be cool to see
uses tracked as we byte-compile or something.

I'm not opposed to reorganizing the code, of course, as long as it
> remains loaded as a command when org-mode is activated.
>

I'm a fan of interactive methods in obvious, easy to reach places.

[-- Attachment #2: Type: text/html, Size: 2083 bytes --]

next prev parent reply	other threads:[~2020-02-13  5:13 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-22  9:04 Provide org-insert-subitem Dmitrii Korobeinikov
2020-02-02  7:49 ` Bastien
2020-02-02 10:11   ` Dmitrii Korobeinikov
2020-02-02 17:43   ` Adam Porter
2020-02-12  8:33     ` Bastien
2020-02-12 21:28       ` Adam Porter
2020-02-13  5:13         ` Corwin Brust [this message]
2020-02-13  8:04         ` Bastien
2020-02-13 18:45           ` Adam Porter
2020-02-14 10:02             ` Bastien
2023-12-08  2:51               ` Adam Porter
2023-12-09 14:09                 ` Ihor Radchenko
2023-12-09 17:53                   ` Bastien Guerry
2023-12-14 15:00                     ` Ihor Radchenko
2023-12-25  9:14                       ` Bastien
2023-12-25  9:40                         ` Ihor Radchenko
2023-12-17  5:59                     ` Adam Porter
2023-12-25  9:21                       ` Bastien

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='CAJf-WoS=O5WVggB7XavBv_FaeVjrNSQauCcOVBE9v3DiKTc==w@mail.gmail.com' \
    --to=corwin@bru.st \
    --cc=adam@alphapapa.net \
    --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

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).