emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Tim Cross <theophilusx@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: Introducing Org-transclusion
Date: Sat, 06 Nov 2021 08:56:16 +1100	[thread overview]
Message-ID: <87pmredzgx.fsf@gmail.com> (raw)
In-Reply-To: <87lf22l6qo.fsf@nobiot.com>


Noboru Ota <me@nobiot.com> writes:

> Timothy <tecosaur@gmail.com> writes:
>
>> It’s worth noting that currently Org’s minimum supported Emacs version is 25. Do
>> you use much from Emacs 26/27? There was mention of compat.el earlier though,
>> and if that goes somewhere this may not be an issue.
>
> Thank you, Timothy.  I take it that support for version 25 to be a
> prerequsite for Org-transclusion to be included in Org.
>
> It never occured to me; thanks for pointing it out.  I will need to
> check -- it was just my development was done mainly on 27.
>
> Does this mean Org contributors have different versions of Emacs (25,
> 26, 27...) and test their patches in every version?  Do you know?
>

The org 'policy' is to support the current released Emacs version and
the two previous versions. Current released version is 27.2, so need to
support 26.* and 25.*. We recently dropped the requirement to support
24.x. Once Emacs 28 is released, support for 25.x can be dropped.

WRT making this part of org-mode core, I'm not in favour. This is no
reflection on the package, which I think is a great addition to the org
ecosystem. My preference would be for this package to be an add-on
package in either ELPA or non-GNU ELPA.

My main reason for this is because I think we should be striving to make
the core org packages as small and easily maintained as possible,
containing the core functionality used by everyone. While this package
has some very useful functionality, I feel it is functionality which
will be used by a subset of users or by others only occasionally.

If, at a later date, it turns out a majority of users use this package,
we can review and if necessary/appropriate, bring the package into org core
(assuming copyright is handed over to FSF).


  reply	other threads:[~2021-11-05 22:12 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-30 11:51 Introducing Org-transclusion Noboru Ota
2021-10-30 12:31 ` Juan Manuel Macías
2021-11-01  9:17   ` Noboru Ota
2021-10-30 13:59 ` Ihor Radchenko
2021-11-01  9:11   ` Noboru Ota
2021-11-01 13:24     ` Ihor Radchenko
2021-11-06 10:43       ` Noboru Ota
2021-11-08 15:07         ` Ihor Radchenko
2021-11-10 21:09           ` Noboru Ota
2021-11-14  8:22             ` Ihor Radchenko
2021-11-14  9:35               ` Ihor Radchenko
2021-11-01 20:07     ` Thomas Paulsen
2021-11-01 21:01       ` Noboru Ota
2021-11-02  5:17     ` Timothy
2021-11-05 19:53       ` Noboru Ota
2021-11-05 21:56         ` Tim Cross [this message]
2021-11-05 23:20           ` Timothy
2021-11-06 10:14             ` Noboru Ota
2021-11-06 10:22               ` Tim Cross
2021-11-06 11:49                 ` Noboru Ota
2021-11-05 17:11 ` Uwe Brauer
2021-11-05 19:24   ` Noboru Ota
2021-11-05 20:15     ` Uwe Brauer
2021-11-05 23:02       ` Noboru Ota
2021-11-06 14:01         ` Uwe Brauer
2021-11-06 14:25         ` Ihor Radchenko
2021-11-06 14:54           ` Noboru Ota
2021-11-06 15:49             ` Uwe Brauer
2021-11-07  7:34               ` Ihor Radchenko
2021-11-07  8:07                 ` Uwe Brauer
2021-11-07  8:30                   ` Ihor Radchenko
2021-11-07 13:25                     ` Uwe Brauer
2021-11-07 13:41                       ` Ihor Radchenko
2021-11-07 13:56                         ` Uwe Brauer
2021-11-05 19:59   ` Noboru Ota
2021-11-05 20:13     ` Uwe Brauer

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=87pmredzgx.fsf@gmail.com \
    --to=theophilusx@gmail.com \
    --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).