From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Daniel Mendler via "Emacs development discussions." Newsgroups: gmane.emacs.devel Subject: Re: Why not include all ELPA packages in an Emacs release? Date: Thu, 30 May 2024 08:33:30 +0200 Message-ID: <87r0djlsg5.fsf@daniel-mendler.de> References: <87bk4ql3u5.fsf@jeremybryant.net> <864jagu9ji.fsf@gnu.org> <871q5ktxfh.fsf@posteo.net> <878qzrx1cd.fsf@posteo.net> Reply-To: Daniel Mendler Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="6622"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Cc: Arash Esbati , Eli Zaretskii , Stefan Kangas , jb@jeremybryant.net, emacs-devel@gnu.org, monnier@iro.umontreal.ca To: Philip Kaludercic Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Thu May 30 08:34:44 2024 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 1sCZN6-0001Wj-91 for ged-emacs-devel@m.gmane-mx.org; Thu, 30 May 2024 08:34:44 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1sCZMd-0007zl-Mw; Thu, 30 May 2024 02:34:15 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1sCZMa-0007z5-5o for emacs-devel@gnu.org; Thu, 30 May 2024 02:34:12 -0400 Original-Received: from server.qxqx.de ([2a01:4f8:c012:9177::1] helo=mail.qxqx.de) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1sCZMV-0006cH-Lx; Thu, 30 May 2024 02:34:11 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=daniel-mendler.de; s=key; h=Content-Type:MIME-Version:Message-ID:Date: References:In-Reply-To:Subject:Cc:To:From:Sender:Reply-To: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date: Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=Fq0UbQqLaopBiDZ1Aqz6nXh+x+hMYFockSABMFJm0dE=; b=pT2tMoDdQnOZh2ybT8MHC5Dt0N ps5OsTkQ7epLHTfHBypzP7tzdTDkYeOgAaS/tCmRb0SheE5NRXqeBlaaAM5VIginga4ejJJHE7aL0 w2TeqBMnFBvQek2SkW82bhNb4oc29EAnHz5WdbjxNigfYq8tnjJNrlSil8SxkBfjUyWA=; In-Reply-To: <878qzrx1cd.fsf@posteo.net> (Philip Kaludercic's message of "Thu, 30 May 2024 06:25:54 +0000") Received-SPF: pass client-ip=2a01:4f8:c012:9177::1; envelope-from=mail@daniel-mendler.de; helo=mail.qxqx.de X-Spam_score_int: -27 X-Spam_score: -2.8 X-Spam_bar: -- X-Spam_report: (-2.8 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.29 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-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.devel:319731 Archived-At: Philip Kaludercic writes: > Arash Esbati writes: > >> Philip Kaludercic writes: >> >>> I am not familiar with cape, >> >> Cape offers CAPFs, but I think one great featuzre is that you can switch >> the CAPF function during completion with something like this in your >> init file: >> >> (use-package cape >> :bind (:map corfu-map >> ("C-c p d" . cape-dabbrev) >> ("C-c p f" . cape-file) >> ("C-c p s" . cape-elisp-symbol) >> ("C-c p w" . ispell-completion-at-point) >> ("C-c p :" . cape-emoji))) > > I tried it out, and it doesn't seem to work that well without something > like corfu or vertico. Generally it seems like an example where > "completion" is misinterpreted to mean "selection". This is not correct. Please stop spreading misinformation like this. Capfs like the ones from Cape can be used to complete in a stepwise manner. Simple examples are cape-dict, cape-dabbrev or cape-file. cape-dabbrev for example predates the builtin dabbrev-capf and works in the same way. Daniel