From: Spyros Roum <spyros.roum@posteo.net>
To: emacs-devel@gnu.org
Subject: Add completion to compilation-read-command
Date: Tue, 24 Dec 2024 08:53:46 +0000 [thread overview]
Message-ID: <f9c63ac9-7e72-4ea8-80cb-09853e6e86b9@posteo.net> (raw)
[-- Attachment #1: Type: text/plain, Size: 983 bytes --]
Hello all,
Recently, I started using `M-x compile` more but as I was used to my
shell suggesting past commands as I type (and tools like atuin), I was
missing auto-complete a lot.
I managed to add this functionality by writing a simple function based
on compilation-read-command that uses completing-read instead of
read-shell-command.
Then I used advice-add to overwrite the
original compilation-read-command with mine.
So far this works well, and as far as I can tell there is no good reason
not to make compile auto-completing, it already has a history that you
can navigate anyway.
With that said, this is the first time I write here and the first time
I'm trying to contribute to emacs, so I'm not sure what the best way to
go from here would be.
I think some decisions would need to be taken, for once I am not sure if
it's acceptable to change the default and make it completing or if there
should be an option for it.
Looking forward to your feedback, thanks
[-- Attachment #2: Type: text/html, Size: 1359 bytes --]
next reply other threads:[~2024-12-24 8:53 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-24 8:53 Spyros Roum [this message]
2024-12-24 11:35 ` Add completion to compilation-read-command 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-24 22:44 ` Philip Kaludercic
2024-12-25 8:26 ` Spyros Roum
2024-12-25 11:33 ` Philip Kaludercic
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=f9c63ac9-7e72-4ea8-80cb-09853e6e86b9@posteo.net \
--to=spyros.roum@posteo.net \
--cc=emacs-devel@gnu.org \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.