From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Philip Kaludercic Newsgroups: gmane.emacs.devel Subject: Re: Why not include all ELPA packages in an Emacs release? Date: Thu, 30 May 2024 07:28:09 +0000 Message-ID: <87zfs7vjw6.fsf@posteo.net> References: <87bk4ql3u5.fsf@jeremybryant.net> <864jagu9ji.fsf@gnu.org> <871q5ktxfh.fsf@posteo.net> <878qzrx1cd.fsf@posteo.net> <87r0djlsg5.fsf@daniel-mendler.de> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="3410"; mail-complaints-to="usenet@ciao.gmane.io" Cc: Arash Esbati , Eli Zaretskii , Stefan Kangas , jb@jeremybryant.net, emacs-devel@gnu.org, monnier@iro.umontreal.ca To: Daniel Mendler Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Thu May 30 09:29:14 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 1sCaDq-0000d7-85 for ged-emacs-devel@m.gmane-mx.org; Thu, 30 May 2024 09:29:14 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1sCaCx-0003HT-9D; Thu, 30 May 2024 03:28:19 -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 1sCaCv-0003GJ-OV for emacs-devel@gnu.org; Thu, 30 May 2024 03:28:17 -0400 Original-Received: from mout01.posteo.de ([185.67.36.65]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1sCaCs-00005I-ES for emacs-devel@gnu.org; Thu, 30 May 2024 03:28:17 -0400 Original-Received: from submission (posteo.de [185.67.36.169]) by mout01.posteo.de (Postfix) with ESMTPS id 9EA59240028 for ; Thu, 30 May 2024 09:28:11 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=posteo.net; s=2017; t=1717054091; bh=rGw1vUPLXD0q52plIQXlLrC9mTDlBXFKR4cpicIzEq8=; h=From:To:Cc:Subject:OpenPGP:Date:Message-ID:MIME-Version: Content-Type:From; b=jwgnR7I/yqVp06L9/MaS8ojioJjr/DttKzBOnov9yCM7fFS6Xh86B9Z0PFEZ353bB qfJhiWjoaLPi5gWf7XYn/FfGRA2QDS+NnT9VKj+o9erqP3qchkfJ8WpyjFBjFlhLHt BQvc9j+RY3FIh9Ji1ZVIRiMpvELNf6QeOc0W/LMu5IMZoOBUi7MU+jD8BOETz4lhU1 jGuuVoeoTTW/lw5fuZeAduE7Hzp6CqPP+MBw4/BvtJfsU+3yCpSR7Z9fDhZTCUCXCD 0NSIzSjd5sSM9P/fu+spvj75Au4keMQW74CXSAFapHakCXKGGoUMGMD0BQonDbJw4x bWq4PGTZr2krA== Original-Received: from customer (localhost [127.0.0.1]) by submission (posteo.de) with ESMTPSA id 4VqdBy1s2fz6twH; Thu, 30 May 2024 09:28:09 +0200 (CEST) In-Reply-To: <87r0djlsg5.fsf@daniel-mendler.de> (Daniel Mendler's message of "Thu, 30 May 2024 08:33:30 +0200") OpenPGP: id=7126E1DE2F0CE35C770BED01F2C3CC513DB89F66; url="https://keys.openpgp.org/vks/v1/by-fingerprint/7126E1DE2F0CE35C770BED01F2C3CC513DB89F66"; preference=signencrypt Received-SPF: pass client-ip=185.67.36.65; envelope-from=philipk@posteo.net; helo=mout01.posteo.de X-Spam_score_int: -43 X-Spam_score: -4.4 X-Spam_bar: ---- X-Spam_report: (-4.4 / 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_MED=-2.3, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01 autolearn=unavailable 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:319732 Archived-At: Daniel Mendler writes: > 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. I understand that, I am just saying that it doesn't feel that natural without something like corfu enabled as well. Or at least with the above configuration, something like cape-emoji with the default in-buffer completion is less comfortable than the built-in C-x 8 e. Same with dabbrev itself vs. cape-dabbrev. > 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. How? When I use M-/, the expansion is replaced in place, while cape-dabbrev behaves more like dabbrev-completion (C-M-/) by prompting me for input. > Daniel -- Philip Kaludercic on peregrine