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: Add completion to compilation-read-command Date: Wed, 25 Dec 2024 11:33:13 +0000 Message-ID: <87ttas80au.fsf@posteo.net> References: <87ttatb9g0.fsf@posteo.net> <87a5clm3p5.fsf@mail.linkov.net> <8734icaegs.fsf@posteo.net> <9a4bb215-561c-468f-97de-7d84fe7adc43@posteo.net> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="6746"; mail-complaints-to="usenet@ciao.gmane.io" Cc: juri@linkov.net, emacs-devel@gnu.org To: Spyros Roum Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Wed Dec 25 12:33:41 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 1tQPdz-0001e6-Ue for ged-emacs-devel@m.gmane-mx.org; Wed, 25 Dec 2024 12:33:40 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1tQPdi-0000Zp-FG; Wed, 25 Dec 2024 06:33:22 -0500 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 1tQPdg-0000Ym-3s for emacs-devel@gnu.org; Wed, 25 Dec 2024 06:33:20 -0500 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 1tQPde-0000dL-3y for emacs-devel@gnu.org; Wed, 25 Dec 2024 06:33:19 -0500 Original-Received: from submission (posteo.de [185.67.36.169]) by mout01.posteo.de (Postfix) with ESMTPS id C265A240027 for ; Wed, 25 Dec 2024 12:33:13 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=posteo.net; s=2017; t=1735126393; bh=sGpvD+ilXXG1J8mfpK4qBFk3P6NE5vZt9Qlp+XAHg6k=; h=From:To:Cc:Subject:Autocrypt:OpenPGP:Date:Message-ID:MIME-Version: Content-Type:From; b=Sjake3YogSdiS9X7mnchpao02x+0TII/0o2FrfCMYzM29WBo7ULVrsZwX/DBDdY6X s4mw6mL0jKeoIyT7mNQZsO5tPR3U3H+QDck6bXAkSnKP988lOD1sIjeUs5O1zcTFjW J4MpSCq5SiLbhNZAFa3ZV0e7Gu3vdsF5ijSnOXENZpxHtWOKgmirIf5voh+0ZqgEC8 QZVJoWjmSeljluvxQ9RHumVVcBipfsG3XgpxtImSF3rd/yAi3Db2dSRtUOxO7HVSzK SW3LJ4RLerAU6HL/VOf12tWF9eLs/Kiw3YmK0Gz2pSrqqoW1Vvq4iRwcL2VFRNut1f 5HrugpIsZBlZQ== Original-Received: from customer (localhost [127.0.0.1]) by submission (posteo.de) with ESMTPSA id 4YJ8lF1zbDz9rxL; Wed, 25 Dec 2024 12:33:13 +0100 (CET) In-Reply-To: <9a4bb215-561c-468f-97de-7d84fe7adc43@posteo.net> (Spyros Roum's message of "Wed, 25 Dec 2024 08:26:50 +0000") Autocrypt: addr=philipk@posteo.net; keydata= mDMEZBBQQhYJKwYBBAHaRw8BAQdAHJuofBrfqFh12uQu0Yi7mrl525F28eTmwUDflFNmdui0QlBo aWxpcCBLYWx1ZGVyY2ljIChnZW5lcmF0ZWQgYnkgYXV0b2NyeXB0LmVsKSA8cGhpbGlwa0Bwb3N0 ZW8ubmV0PoiWBBMWCAA+FiEEDg7HY17ghYlni8XN8xYDWXahwukFAmQQUEICGwMFCQHhM4AFCwkI BwIGFQoJCAsCBBYCAwECHgECF4AACgkQ8xYDWXahwulikAEA77hloUiSrXgFkUVJhlKBpLCHUjA0 mWZ9j9w5d08+jVwBAK6c4iGP7j+/PhbkxaEKa4V3MzIl7zJkcNNjHCXmvFcEuDgEZBBQQhIKKwYB BAGXVQEFAQEHQI5NLiLRjZy3OfSt1dhCmFyn+fN/QKELUYQetiaoe+MMAwEIB4h+BBgWCAAmFiEE Dg7HY17ghYlni8XN8xYDWXahwukFAmQQUEICGwwFCQHhM4AACgkQ8xYDWXahwukm+wEA8cml4JpK NeAu65rg+auKrPOP6TP/4YWRCTIvuYDm0joBALw98AMz7/qMHvSCeU/hw9PL6u6R2EScxtpKnWof z4oM OpenPGP: id=philipk@posteo.net; url="https://keys.openpgp.org/vks/v1/by-email/philipk@posteo.net"; 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, RCVD_IN_VALIDITY_CERTIFIED_BLOCKED=0.001, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, 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.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:327068 Archived-At: Spyros Roum writes: > Philip Kaludercic wrote: >> Spyros Roum writes: >> >>> Juri Linkov wrote: >>>>> I'm trying to get the compile prompt to suggest completion based on past >>>>> commands I've run. >>>> You can use 'C-x ' in the compile prompt to complete on past commands. >>> This is indeed a lot closer to what I want, however it still lacks a >>> lot of things compared to my solution. >>> >>> Unless there is some package/mode I don't know about, It's a lot less >>> dynamic, for instance I can't keep typing to reduce >>> possible items. >> One should keep in mind that completion is not the same as narrowing. >> The former expands substrings, while the latter is more like a system >> for selecting an option from a list, that usually comes with some query >> system. >> Confusing these two can lead to uncomfortable >> edge-cases for both sides, >> and sadly a lot of packages assume that completing-read is the same as a >> hypothetical selecting-read. > I was 100% confusing these two, thanks for clearing it up. np. > To make sure I understand correctly, when using `completing-read` to > read user input, that is narrowing, > while the `C-x ` and *Completions* buffer is completion. No, `completing-read' just invokes an interface, that frontends can implement a UI for. The default UI provides a completing/expanding interface, while Vertico, Helm, Ivy, etc. do selecting/narrowing. When using `completing-read' you cannot really assume one or the other, so in effect one has to find a middle ground. It is best you try your code in emacs -Q without any changes and see how it behaves. Things like SPC doing something else than you would expect is just one pitfall, others I can recall are providing text that is difficult to input (I wrote a package a few years back called "insert-kaomoji" that used `completing-read' to prompt the user eastern-style emoticons; it is easy to use with a selecting framework, but more inconvenient if the user is first made to complete a string that is difficult to write, as most of the characters are not easy to type). > And from > this thread I learned that Icicles can be used to enhance completion > similarly to how narrowing frameworks (like vertico) enhance narrowing. I have never used it, because it is not available as a package and it redefines built-in functions, but my understanding it that it is something similar. >>> My solution can leverage all of vertico and friend, and in general >>> provides an experience that's the same as other minibuffer prompts, >>> like M-x. >> But for someone like me who doesn't use a selecting-narrowing framework >> like vertico, it suddenly means that SPC is rebound to >> `minibuffer-complete-word' and entering new commands becomes *a lot* more >> cumbersome. > And this is where the user option for the function would come in useful. Right, and I just wanted to second Juri's suggestion for the name.