From: Tim Cross <theophilusx@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: Suggestion: convert dispatchers to use transient
Date: Fri, 04 Feb 2022 08:30:23 +1100 [thread overview]
Message-ID: <87wnibr5hq.fsf@gmail.com> (raw)
In-Reply-To: <d4d614f4-5b56-8683-6051-476c47fde07d@gmail.com>
Jim Porter <jporterbugs@gmail.com> writes:
> On 2/3/2022 2:07 AM, Tim Cross wrote:
>> After 28.0 is released, if transient is a GNU ELPA package, we can
>> probably just make it an org dependency and Emacs 26.x and 27.x should
>> be able to install and run it (would need to be verified).
>
> The transient package is on GNU ELPA already[1], and based on its package
> metadata[2], supports Emacs 25.1+, so I don't think there should be any
> compatibility concerns (at least not with the availability of transient; maybe
> there are other reasons that dispatchers shouldn't change without an option to
> go back).
>
> - Jim
>
> [1] https://elpa.gnu.org/packages/transient.html
> [2]
> https://github.com/magit/transient/blob/440a341831398b825dc2288a10821cf7be1999ca/lisp/transient.el#L9
That is good to know. I knew it was getting added, but wasn't sure how
compatible it would be with older versions.
Not 100% sure about best migration strategy. On one level, providing the
ability for users to choose which interface sounds nice, but on the
other, a main goal is to simplify code and reduce maintenance. Providing
a choice will actually complicate matters and increase maintenance.
Is the transient.el included in Emacs 28 the same as the one on GNU
ELPA? I'm assuming it is, but I have to admit I'm still not 100% clear
on how Emacs handles the situation where you use a library that is both
built-in and available in ELPA. Does Emacs use the latest version
available or does it use the built-in version until you explicitly
select the ELPA versions?
next prev parent reply other threads:[~2022-02-03 22:09 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-02 11:59 Suggestion: convert dispatchers to use transient Hugo Heagren
2022-02-03 8:54 ` Tom Gillespie
2022-02-03 10:07 ` Tim Cross
2022-02-03 17:51 ` Jim Porter
2022-02-03 21:30 ` Tim Cross [this message]
2022-02-04 1:13 ` Jim Porter
2022-02-04 5:37 ` Christopher M. Miles
2022-02-05 20:18 ` João Pedro de Amorim Paula
2022-02-06 1:49 ` Samuel Wales
2022-02-06 3:28 ` João Pedro de Amorim Paula
2022-02-07 15:37 ` Anders Johansson
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=87wnibr5hq.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).