emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Bastien <bzg@gnu.org>
To: William Rankin via "General discussions about Org-mode."
Cc: William Rankin <william@bydasein.com>, emacs-devel@gnu.org
Subject: Re: Re Org 9.4 is out. Can you help? // breaking apart Org Mode
Date: Wed, 23 Sep 2020 10:21:21 +0200	[thread overview]
Message-ID: <87pn6c29a6.fsf@gnu.org> (raw)
In-Reply-To: <m2imcfmk2n.fsf@bydasein.com> (William Rankin via's message of "Tue, 15 Sep 2020 20:05:20 +1000")

Hi William,

thanks a lot for bringing this up.

Of course, Org would benefit from code cleanup and code refactoring.

And yes, we can collectively push toward (1) modularizing Org a little
more, (2) making Org features better interact with Emacs core features
and (3) integrating some of Org's features into Emacs core as Emacs

IMHO the good examples you give fall into one of the category above,
and I think such efforts are likely to happen in that order: 1, 2, 3.

The better way to make this happen is to start a discussion with a
patch explaining how it makes 1, 2 or 3, then discussing the patch
here on this list - the smaller the better.

If you cannot make a patch, first discuss your idea, and once the
implementation seems clear, call for help by using a mail header:

  X-Woof-Help: Help with making X a new module



  parent reply	other threads:[~2020-09-23  8:21 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-15 10:05 Re Org 9.4 is out. Can you help? // breaking apart Org Mode William Rankin via General discussions about Org-mode.
2020-09-15 13:00 ` Nicholas Savage
2020-09-15 13:49   ` Russell Adams
2020-09-23  8:28     ` Bastien
2020-09-23 14:44       ` Dr. Arne Babenhauserheide
2020-09-23  8:25   ` Bastien
2020-09-23  8:21 ` Bastien [this message]
2020-09-23 13:03   ` arthur miller
2020-09-23 13:27     ` Ihor Radchenko

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:

  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=87pn6c29a6.fsf@gnu.org \
    --to=bzg@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=emacs-orgmode@gnu.org \
    --cc=william@bydasein.com \


* 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


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