From: Visuwesh <visuweshm@gmail.com>
To: Spyros Roum <spyros.roum@posteo.net>
Cc: philipk@posteo.net, juri@linkov.net, emacs-devel@gnu.org
Subject: Re: Add completion to compilation-read-command
Date: Thu, 26 Dec 2024 18:48:13 +0530 [thread overview]
Message-ID: <87ldw2d1m2.fsf@gmail.com> (raw)
In-Reply-To: <25958644-5b99-4611-b6ae-ce8448fb662f@posteo.net> (Spyros Roum's message of "Thu, 26 Dec 2024 13:13:30 +0000")
[வியாழன் டிசம்பர் 26, 2024] Spyros Roum wrote:
I don't really have much to say about the change but:
> [...]
> I based the entry on a similar entry from a few lines up:
>
> > *** New user option 'completion-pcm-leading-wildcard'.
> > This option configures how the partial-completion style does
> completion.
> > It defaults to nil, which preserves the existing behavior. When it
> is set
> > to t, the partial-completion style behaves more like the substring
> > style, in that a string being completed can match against a candidate
> > anywhere in the candidate string.
>
> If you think however that the options are not necessary, I can keep
> the first sentence only.
>
> Patch attached has the corrected `:version` and ChangeLog, no other
> changes (also rebased to master).
> From fa17714fcb12079bc37e5be54fe6b2a68bcd34ff 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
> [...]
> diff --git a/lisp/progmodes/compile.el b/lisp/progmodes/compile.el
> index 6784a12fd63..d0da96069af 100644
> --- a/lisp/progmodes/compile.el
> +++ b/lisp/progmodes/compile.el
> @@ -1797,12 +1797,38 @@ 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-with-history-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
> + "`compilation-read-command' uses this function to get user's input.
> +Defaults to `compilation-prompt-read-shell-command',
> +but 'compilation-prompt-read-with-history-completion' can be used instead for
> +a completing version based on past runs."
> + :version "31.1"
> + :type 'function
> + :options
> + (list
> + #'compilation-prompt-read-shell-command
> + #'compilation-prompt-read-with-history-completion))
It would be nice to say what these options mean in plain English (with
:tag IIRC).
next prev parent reply other threads:[~2024-12-26 13:18 UTC|newest]
Thread overview: 31+ 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
2024-12-25 16:38 ` Philip Kaludercic
2024-12-25 22:11 ` Spyros Roum
2024-12-26 11:39 ` Philip Kaludercic
2024-12-26 13:13 ` Spyros Roum
2024-12-26 13:18 ` Visuwesh [this message]
2024-12-26 14:46 ` Spyros Roum
2024-12-26 15:04 ` Visuwesh
2024-12-26 16:00 ` 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=87ldw2d1m2.fsf@gmail.com \
--to=visuweshm@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=juri@linkov.net \
--cc=philipk@posteo.net \
--cc=spyros.roum@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).