From: Bastien <bzg@gnu.org>
To: Adam Porter <adam@alphapapa.net>
Cc: emacs-orgmode@gnu.org
Subject: Re: Provide org-insert-subitem
Date: Thu, 13 Feb 2020 09:04:25 +0100 [thread overview]
Message-ID: <87mu9m7w1i.fsf@bzg.fr> (raw)
In-Reply-To: 87sgjflclf.fsf@alphapapa.net
Hi Adam,
First of all, don't be afraid, I don't have a grand plan for "cleaning
up" things.
> I'm not sure what you mean about functions mentioned as usable by the
> user. org-insert-subheading is an interactive command, so it's
> explicitly usable by the user.
Yes, org-insert-subheading is interactive and usable and in Org's core
but how can a user *discover* this command?
There is no keybinding for it and no mention in the manual. Even as a
function, it is not even used in Org codebase.
The ways I can see for a user to discover this command is by trying to
complete M-x org-insert TAB or by reading Org's code (or other code in
the wild using it.)
So to me it's a "utility" command: something that Org does not depend
on, something that provides a useful feature, but not useful enough to
have a keybinding in Org's core or to be used as a function in Org's
core.
> And it's in org.el, so it's in Org's
> "core", right? I guess we're thinking in different terms.
Well, my thinking is not about core vs not-core, it is more on how to
advertize such commands and functions. I would recommand putting them
in org-utils.el but I'm not sure. And yes, I'm not entirely convinced
such a library, if it existed, should live in Org's core :)
Best,
--
Bastien
next prev parent reply other threads:[~2020-02-13 8:04 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
2020-02-13 8:04 ` Bastien [this message]
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=87mu9m7w1i.fsf@bzg.fr \
--to=bzg@gnu.org \
--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
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).