From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.devel Subject: Re: [elpa] main 8f4cb59: * elpa-packages (counsel, ivy, swiper): Auto-sync. Date: Thu, 11 Mar 2021 12:34:18 -0500 Message-ID: References: <20210225102521.11653.64611@vcs0.savannah.gnu.org> <20210225102523.7CEF420B28@vcs0.savannah.gnu.org> <87h7m0z07r.fsf@tcd.ie> <87mtvsundg.fsf@tcd.ie> <875z20m0oa.fsf@tcd.ie> <87eegn18rr.fsf@tcd.ie> <87im5x8vil.fsf@tcd.ie> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="5440"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/28.0.50 (gnu/linux) Cc: emacs-devel@gnu.org, Oleh Krehel To: "Basil L. Contovounesios" Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Thu Mar 11 18:42:49 2021 Return-path: Envelope-to: ged-emacs-devel@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1lKPKj-0001Im-NZ for ged-emacs-devel@m.gmane-mx.org; Thu, 11 Mar 2021 18:42:49 +0100 Original-Received: from localhost ([::1]:53748 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1lKPKi-0002xr-Pv for ged-emacs-devel@m.gmane-mx.org; Thu, 11 Mar 2021 12:42:48 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:38876) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1lKPCc-0003hB-9k for emacs-devel@gnu.org; Thu, 11 Mar 2021 12:34:26 -0500 Original-Received: from mailscanner.iro.umontreal.ca ([132.204.25.50]:54848) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1lKPCZ-0005Az-Ct for emacs-devel@gnu.org; Thu, 11 Mar 2021 12:34:25 -0500 Original-Received: from pmg1.iro.umontreal.ca (localhost.localdomain [127.0.0.1]) by pmg1.iro.umontreal.ca (Proxmox) with ESMTP id 96E1610023D; Thu, 11 Mar 2021 12:34:21 -0500 (EST) Original-Received: from mail01.iro.umontreal.ca (unknown [172.31.2.1]) by pmg1.iro.umontreal.ca (Proxmox) with ESMTP id F0FAE1001D2; Thu, 11 Mar 2021 12:34:19 -0500 (EST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=iro.umontreal.ca; s=mail; t=1615484059; bh=dCV8HHD4NZz1/03mNoUBrMToONeNlwTTtIZRONc1Dgs=; h=From:To:Cc:Subject:References:Date:In-Reply-To:From; b=icBtWuFNW2/UOrPo4n3GQA5fc5bKaYo3NLC/0K2OnSsdAsQI6Z1M2VRWOH+4YtUKD 0Gkp8++xA6HD6L+78Yuih1OiBuysTdSLpH/zZWUr0l6VcaajbL68J8tz6ucEZTDt9X ch34LUoGHJrV5Fvatx+LLHpFUb0DecoqmUI5pmeqIxnWVN9GlILTxqyu3lUs1drDaU qRU1uoSBJ5Bd/CvBs3Wpy/ulixp/mfWTt3UdVusom7Ky+s1RvJTYdMLluDuboyLHSK Ch3JoXhJht9sCnq/UAKRn3tpc5Jb0tGNIROb3CkwayhDHEUDxoYITYsOYnEOylgQ10 /WCfGB7dSxJtA== Original-Received: from alfajor (unknown [216.154.43.249]) by mail01.iro.umontreal.ca (Postfix) with ESMTPSA id B67D31201A9; Thu, 11 Mar 2021 12:34:19 -0500 (EST) In-Reply-To: <87im5x8vil.fsf@tcd.ie> (Basil L. Contovounesios's message of "Thu, 11 Mar 2021 17:12:18 +0000") Received-SPF: pass client-ip=132.204.25.50; envelope-from=monnier@iro.umontreal.ca; helo=mailscanner.iro.umontreal.ca X-Spam_score_int: -42 X-Spam_score: -4.3 X-Spam_bar: ---- X-Spam_report: (-4.3 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_PASS=-0.001 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.io gmane.emacs.devel:266342 Archived-At: > 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`. 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`? >> Fetching tags from upstream is problematic (because we have a single >> elpa.git repository for all packages), but we could use tags manually >> pushed to elpa.git, yes. > I was thinking of the latter indeed, as a more "Git-native" way of > pointing to a release. That'd be fine by me. > I can't promise to implement any of these features for another few > months though (at least not without a guilty conscience ;). Oh, if you need an extra guilty conscience in order to get to work, I can help, I have plenty of those here. Stefan