From: Spyros Roum <spyros.roum@posteo.net>
To: philipk@posteo.net
Cc: juri@linkov.net, emacs-devel@gnu.org
Subject: Re: Add completion to compilation-read-command
Date: Wed, 25 Dec 2024 15:44:42 +0000 [thread overview]
Message-ID: <962064f8-fab7-4867-af04-135e48a9dd15@posteo.net> (raw)
In-Reply-To: <87ttas80au.fsf@posteo.net>
[-- Attachment #1.1: Type: text/plain, Size: 1784 bytes --]
Philip Kaludercic wrote:
>> To make sure I understand correctly, when using `completing-read` to
>> read user input, that is narrowing,
>> while the `C-x <up>` 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).
I tried the attached patch with `emacs -q` and now I understand how this
would be very annoying without something like vertico installed haha.
Nevertheless, it seems to work!
I'm attaching a patch based on the conversation so far to get feedback on.
I believe I should also write something to the NEWS file.
Also, I'm wondering if this counts as non-trivial enough that I would
need to sign the FSF copyright.
Regarding testing, as far as I can tell, there are currently no tests
for `compilation-read-command`.
Should I add anything? If yes, I'll probably need someone to point to
existing tests for similar things that I can copy from.
Am I forgetting anything else?
[-- Attachment #1.2: Type: text/html, Size: 2502 bytes --]
[-- Attachment #2: 0001-Add-option-for-making-compilation-read-command-use-c.patch --]
[-- Type: text/x-patch, Size: 2018 bytes --]
From e1068206662913978d541f924205a0615f8d2d95 Mon Sep 17 00:00:00 2001
From: Spyros Roum <spyros.roum@posteo.net>
Date: Wed, 25 Dec 2024 17:32:31 +0200
Subject: [PATCH] Add option for making compilation-read-command use
completing-read
---
lisp/progmodes/compile.el | 24 +++++++++++++++++++++++-
1 file changed, 23 insertions(+), 1 deletion(-)
diff --git a/lisp/progmodes/compile.el b/lisp/progmodes/compile.el
index 6784a12fd63..a318937e96d 100644
--- a/lisp/progmodes/compile.el
+++ b/lisp/progmodes/compile.el
@@ -1797,12 +1797,34 @@ compilation-mode-font-lock-keywords
'((compilation--ensure-parse))
compilation-mode-font-lock-keywords))
-(defun compilation-read-command (command)
+(defun compilation-prompt-read-shell-command (command)
(read-shell-command "Compile command: " command
(if (equal (car compile-history) command)
'(compile-history . 1)
'compile-history)))
+(defun compilation-prompt-read-command-with-completion (command)
+ (completing-read "Compile command: " compile-history
+ nil nil command
+ (if (equal (car compile-history) command)
+ '(compile-history . 1)
+ 'compile-history)))
+
+(defcustom compilation-read-command-function
+ 'compilation-prompt-read-shell-command
+ "Function used by `compilation-read-command' to get user's input.
+Defaults to `compilation-prompt-read-shell-command',
+but `compilation-prompt-read-command-with-completion' can be used instead for
+a completing version based on past runs."
+ :version "31.0"
+ :type 'function
+ :options '(compilation-prompt-read-command-with-completion))
+
+(defun compilation-read-command (command)
+ "Prompt user for command to run.
+`compilation-read-command-function' controls the way input is read from the minibuffer."
+ (funcall compilation-read-command-function command))
+
\f
;;;###autoload
(defun compile (command &optional comint)
--
2.47.1
next prev parent reply other threads:[~2024-12-25 15:44 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-24 8:53 Add completion to compilation-read-command Spyros Roum
2024-12-24 11:35 ` Philip Kaludercic
2024-12-24 11:57 ` Spyros Roum
2024-12-24 12:53 ` Philip Kaludercic
2024-12-24 13:43 ` Spyros Roum
2024-12-24 14:53 ` Philip Kaludercic
2024-12-24 17:03 ` Juri Linkov
2024-12-24 18:36 ` Spyros Roum
2024-12-24 18:50 ` Juri Linkov
2024-12-24 18:59 ` Spyros Roum
2024-12-24 22:35 ` Philip Kaludercic
2024-12-25 7:27 ` Juri Linkov
2024-12-24 19:56 ` [External] : " Drew Adams
2024-12-25 7:29 ` Juri Linkov
2024-12-25 19:46 ` Drew Adams
2024-12-24 22:44 ` Philip Kaludercic
2024-12-25 8:26 ` Spyros Roum
2024-12-25 11:33 ` Philip Kaludercic
2024-12-25 15:44 ` Spyros Roum [this message]
2024-12-25 16:38 ` Philip Kaludercic
2024-12-25 22:11 ` Spyros Roum
2024-12-25 17:32 ` Juri Linkov
2024-12-25 18:02 ` Spyros Roum
2024-12-25 19:36 ` [External] : " Drew Adams
2024-12-24 19:27 ` Eli Zaretskii
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=962064f8-fab7-4867-af04-135e48a9dd15@posteo.net \
--to=spyros.roum@posteo.net \
--cc=emacs-devel@gnu.org \
--cc=juri@linkov.net \
--cc=philipk@posteo.net \
/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).