From: Jonas Bernoulli <jonas@bernoul.li>
To: Stephen Leake <stephen_leake@stephe-leake.org>
Cc: "Óscar Fuentes" <ofv@wanadoo.es>, "Doug Davis" <ddavis@ddavis.io>,
emacs-devel@gnu.org, Clemens <clemens.radermacher@posteo.de>,
"Kévin Le Gouguec" <kevin.legouguec@gmail.com>,
"Lars Ingebrigtsen" <larsi@gnus.org>,
"Stefan Monnier" <monnier@iro.umontreal.ca>
Subject: Re: A different way to interactively pass options to commands
Date: Tue, 23 Feb 2021 20:06:33 +0100 [thread overview]
Message-ID: <8735xma9ja.fsf@bernoul.li> (raw)
In-Reply-To: <8635xn6kuw.fsf@stephe-leake.org>
Stephen Leake <stephen_leake@stephe-leake.org> writes:
> Jonas Bernoulli <jonas@bernoul.li> writes:
>
>>> What are your thoughts about the discussion of including it in Emacs?
>>> I think having it built-in would be a huge benefit.
>>
>> I would prefer the "bundled elpa package" approach over adding the
>> package to emacs.git itself, but don't know if that feature is already
>> usable.
>
> Since transient is a single elisp file, the simplest approach is to put
> it in emacs.git under lisp, and enter it in elpa as a :core package.
> Then emacs.git is the upstream development repo.
Plus transient.texi.
Does that change anything?
> The proposed policy for bundled elpa packages is that core emacs code
> may not depend on them; on the other hand, core emacs code may depend on
> :core elpa packages.
Well that decides it then; core it is.
next prev parent reply other threads:[~2021-02-23 19:06 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-17 19:50 A different way to interactively pass options to commands Clemens
2021-02-17 20:07 ` Stefan Monnier
2021-02-17 20:20 ` Lars Ingebrigtsen
2021-02-17 22:05 ` Stefan Monnier
2021-02-19 5:41 ` Richard Stallman
2021-02-19 14:30 ` Stefan Monnier
2021-02-17 20:09 ` Lars Ingebrigtsen
2021-02-17 20:32 ` Clemens
2021-02-17 20:42 ` Lars Ingebrigtsen
2021-02-17 20:58 ` Clemens
2021-02-17 21:24 ` Clemens
2021-02-17 22:15 ` Stefan Monnier
2021-02-17 21:48 ` Óscar Fuentes
2021-02-17 22:23 ` Stefan Monnier
2021-02-17 22:47 ` Óscar Fuentes
2021-02-17 23:52 ` Clemens
2021-02-17 22:24 ` Lars Ingebrigtsen
2021-02-17 23:18 ` Óscar Fuentes
2021-02-18 10:09 ` Lars Ingebrigtsen
2021-02-18 1:16 ` Doug Davis
2021-02-18 10:03 ` Lars Ingebrigtsen
2021-02-18 10:39 ` Kévin Le Gouguec
2021-02-18 10:52 ` Lars Ingebrigtsen
2021-02-18 12:13 ` Dmitry Gutov
2021-02-18 17:45 ` Stefan Kangas
2021-02-18 17:55 ` Dmitry Gutov
2021-02-18 18:32 ` Stefan Kangas
2021-02-19 11:59 ` Lars Ingebrigtsen
2021-02-18 16:11 ` Óscar Fuentes
2021-02-18 15:40 ` Stefan Monnier
2021-02-18 16:28 ` Development snapshots on GNU ELPA (was: A different way to interactively pass options to commands) Kévin Le Gouguec
2021-02-19 12:01 ` A different way to interactively pass options to commands Lars Ingebrigtsen
2021-02-19 14:32 ` Stefan Monnier
2021-02-21 14:55 ` GNU-devel and NonGNU-devel (was: A different way to interactively pass options to commands) Basil L. Contovounesios
2021-02-21 20:25 ` GNU-devel and NonGNU-devel Stefan Monnier
2021-02-25 2:19 ` Basil L. Contovounesios
2021-02-19 15:44 ` A different way to interactively pass options to commands Jonas Bernoulli
2021-02-19 18:23 ` Clemens
2021-02-22 0:18 ` Jonas Bernoulli
2021-02-22 2:39 ` T.V Raman
2021-02-22 9:17 ` Questions about transient (was: Re: A different way to interactively pass options to commands) Joost Kremers
2021-02-22 15:08 ` Jonas Bernoulli
2021-02-22 21:06 ` Joost Kremers
2021-02-22 16:25 ` [External] : " Drew Adams
2021-02-23 12:15 ` A different way to interactively pass options to commands Stephen Leake
2021-02-23 19:06 ` Jonas Bernoulli [this message]
2021-02-19 5:42 ` Richard Stallman
2021-02-19 6:32 ` Stefan Kangas
2021-02-21 10:28 ` Phil Sainty
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.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8735xma9ja.fsf@bernoul.li \
--to=jonas@bernoul.li \
--cc=clemens.radermacher@posteo.de \
--cc=ddavis@ddavis.io \
--cc=emacs-devel@gnu.org \
--cc=kevin.legouguec@gmail.com \
--cc=larsi@gnus.org \
--cc=monnier@iro.umontreal.ca \
--cc=ofv@wanadoo.es \
--cc=stephen_leake@stephe-leake.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.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).