From: "Basil L. Contovounesios" <contovob@tcd.ie>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: emacs-devel@gnu.org, Oleh Krehel <oleh@oremacs.com>
Subject: Re: [elpa] main 8f4cb59: * elpa-packages (counsel, ivy, swiper): Auto-sync.
Date: Thu, 11 Mar 2021 19:25:57 +0000 [thread overview]
Message-ID: <87eegl7are.fsf@tcd.ie> (raw)
In-Reply-To: <jwvzgz9lie9.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Thu, 11 Mar 2021 12:34:18 -0500")
Stefan Monnier <monnier@iro.umontreal.ca> writes:
>> The packages ivy-avy and ivy-hydra are considered optional integrations
>> with the separate packages avy and hydra, respectively, so they seem
>> like the best candidates for splitting into separate packages (or
>> merging with the avy and hydra packages, I think).
>
> `ivy-hydra` seems to be "extra `ivy` functionality, using a hydra",
> rather than "`ivy` support for hydras", so I don't think it belongs with
> `hydra.el`.
>
> OTOH, I think it should be included into `ivy`. IIUC this is currently
> not done because it would require adding `hydra` as a dependency to
> `ivy`, but my counter argument would be that the better option is to add
> to `hydra` a new *function* to replace/complement the `defhydra`
> *macro*, so that `ivy-hydra.el` can be included into `ivy` (and compiled
> correctly) without needing to add a dependency on `hydra`.
Right.
> For `ivy-avy` I think the argument is almost the same, except I don't
> see any reason why it isn't done yet (there doesn't seem to be any need
> for `avy` to be around to compile correctly `ivy-avy`).
>
> So, let's start with this: Could we merge `ivy-avy` into `ivy`?
That's where it was until last year:
https://git.savannah.gnu.org/cgit/emacs/elpa.git/commit/?id=6a576cba564ab8860142f9ec343b13ec89cc2440
Thanks,
--
Basil
next prev parent reply other threads:[~2021-03-11 19:25 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20210225102521.11653.64611@vcs0.savannah.gnu.org>
[not found] ` <20210225102523.7CEF420B28@vcs0.savannah.gnu.org>
2021-02-25 14:33 ` [elpa] main 8f4cb59: * elpa-packages (counsel, ivy, swiper): Auto-sync Basil L. Contovounesios
2021-02-25 15:12 ` Stefan Monnier
2021-02-25 16:24 ` Basil L. Contovounesios
2021-02-25 16:40 ` Stefan Monnier
2021-03-09 22:17 ` Basil L. Contovounesios
2021-03-09 23:56 ` Stefan Monnier
2021-03-10 12:40 ` Basil L. Contovounesios
2021-03-11 15:48 ` Stefan Monnier
2021-03-11 17:12 ` Basil L. Contovounesios
2021-03-11 17:34 ` Stefan Monnier
2021-03-11 19:25 ` Basil L. Contovounesios [this message]
2021-03-11 22:47 ` Stefan Monnier
2021-03-11 22:59 ` Basil L. Contovounesios
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=87eegl7are.fsf@tcd.ie \
--to=contovob@tcd.ie \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=oleh@oremacs.com \
/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).