all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Joost Kremers <joostkremers@fastmail.fm>
To: Bithov Vinu <bithov.vinub@gmail.com>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Using unmaintained plugins
Date: Sun, 18 Apr 2021 22:03:50 +0200	[thread overview]
Message-ID: <877dkzwdft.fsf@fastmail.fm> (raw)
In-Reply-To: <CAH4qOOs2RgEC93Cah2yJh8d6jJ4m90hkR=_571pvPf3xfqnREQ@mail.gmail.com>


On Sun, Apr 18 2021, Bithov Vinu wrote:
> My question is, is there any concern over using a plugin that is
> unmaintained? If it was written in something like C, I could rest assured
> that the C standard is not going to change so drastically in the
> foreseeable future that I won't be able to compile it, but I'm lost in this
> regard with Emacs and Emacs Lisp.

Emacs Lisp does change, more so probably than C, but backward compatibility is
always a top priority, so as far as the language itself is concerned, it would
normally take many years before code becomes so stale that it won't compile
anymore.

The bigger concern is the Emacs environment. A package may make assumptions
about the environment it is used in that stop being true at some point. Case in
point, I used to use a plugin for mu4e (an Emacs-based e-mail client) that made
particular assumptions about the way mu4e's main screen was built up. At some
point, the way this was done changed and the plugin stopped working. It still
compiled fine, but it didn't work anymore.

`org-drill` obviously relies on Org mode, which may not be as strict about
backward compatibility as Emacs itself, but its core functionality won't change,
so most Org-based packages should work just fine even if they are a couple of
years old.

But, as you may guess from all the hedging, there are no guarantees.


-- 
Joost Kremers
Life has its moments



  reply	other threads:[~2021-04-18 20:03 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-18  9:35 Using unmaintained plugins Bithov Vinu
2021-04-18 20:03 ` Joost Kremers [this message]
2021-04-18 22:21 ` Jean Louis
2021-04-19  6:51   ` Marcin Borkowski
2021-04-19  7:34     ` Jean Louis
2021-04-19  8:12     ` Bithov Vinu
2021-04-19  9:40       ` Bithov Vinu
2021-04-19 10:29       ` Jean Louis
2021-04-19 20:16         ` Bithov Vinu
2021-04-20  6:35           ` Jean Louis
2021-04-20 20:19             ` Bithov Vinu
2021-04-21  4:03               ` Jean Louis
  -- strict thread matches above, loose matches on Subject: below --
2021-04-18 18:23 phillip.lord

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=877dkzwdft.fsf@fastmail.fm \
    --to=joostkremers@fastmail.fm \
    --cc=bithov.vinub@gmail.com \
    --cc=help-gnu-emacs@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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.