From: Drew Adams <drew.adams@oracle.com>
To: Juri Linkov <juri@linkov.net>, Spyros Roum <spyros.roum@posteo.net>
Cc: "philipk@posteo.net" <philipk@posteo.net>,
"emacs-devel@gnu.org" <emacs-devel@gnu.org>
Subject: RE: [External] : Re: Add completion to compilation-read-command
Date: Tue, 24 Dec 2024 19:56:38 +0000 [thread overview]
Message-ID: <DS7PR10MB523276A95C2A1F34F27DA91AF3032@DS7PR10MB5232.namprd10.prod.outlook.com> (raw)
In-Reply-To: <87o710j4pf.fsf@mail.linkov.net>
> >> You can use 'C-x <up>' 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.
>
> There were many proposals how to implement `eager-update' to update
> *Completions* as you type. We just need to put together all parts.
Taking me back...
Icicles has had all of that since 2006.
https://www.emacswiki.org/emacs/Icicles_-_History_Enhancements
https://www.emacswiki.org/emacs/Icicles_-_Nutshell_View#ProgressiveCompletion
https://www.emacswiki.org/emacs/Icicles_-_Nutshell_View#ChippingAway
https://www.emacswiki.org/emacs/Icicles_-_Icompletion#IncrementalCompletion
https://www.emacswiki.org/emacs/Icicles_-_Progressive_Completion
next prev parent reply other threads:[~2024-12-24 19:56 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 ` Drew Adams [this message]
2024-12-25 7:29 ` [External] : " 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
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=DS7PR10MB523276A95C2A1F34F27DA91AF3032@DS7PR10MB5232.namprd10.prod.outlook.com \
--to=drew.adams@oracle.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).