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

From: Bithov Vinu <bithov.vinub@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Backwards compatability
Date: Thu, 22 Apr 2021 18:41:41 +0100	[thread overview]
Message-ID: <CAH4qOOutEQze0MqE_v3_nnq+AHj+=mfPb-OHUE_ZTQ=irdhkxA@mail.gmail.com> (raw)

Hi,

I recently posted to the help-gnu-emacs mailing list about using the
org-mode package "org-drill" and its long-term viability considering
that it is no longer actively maintained - you can see the thread
[here](https://lists.gnu.org/archive/html/help-gnu-emacs/2021-04/msg00230.html).

The responses I got often pointed to the fact that while Emacs Lisp
tries to strictly say backwards-compatible, there may be no guarantee
for OrgMode, the functions of which (as well as some other misc.
libraries) org-drill relies on.

Are any measures being done to make org-mode backwards compatible, so
that older plugins aren't crippled by new updates? A cursory
DuckDuckGo yields
[this](https://news.ycombinator.com/item?id=10636589) HackerNews
comment, which seems to suggest that the "developers don't care at all
about breakage". This may still hold true, but the comment was written
in 2015 and I wanted to make sure so that I could:

(a) proceed with educated caution using org-drill, fixing bugs where necessary
(b) using an alternate spaced repetition application, ie.
Anki/Mnemosyne (the two open source flashcard applications)

Thanks,
~~~

next             reply	other threads:[~2021-04-22 17:44 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-22 17:41 Bithov Vinu [this message]
2021-04-25  4:39 ` Backwards compatability Bastien
2021-04-25 21:00   ` Nick Savage
     [not found] <df46ea4a506948a89db854e2ae1d35a0@VI1PR0102MB3327.eurprd01.prod.exchangelabs.com>
2021-04-23  8:10 ` Eric S Fraga

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='CAH4qOOutEQze0MqE_v3_nnq+AHj+=mfPb-OHUE_ZTQ=irdhkxA@mail.gmail.com' \
    --to=bithov.vinub@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

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