From: "T.V Raman" <raman@google.com>
To: tsdh@gnu.org
Cc: raman@google.com, emacs-devel@gnu.org
Subject: Re: [GNU ELPA] New package proposal: aggressive-completion.el
Date: Mon, 5 Apr 2021 07:21:32 -0700 [thread overview]
Message-ID: <24683.7404.791668.929210@retriever.mtv.corp.google.com> (raw)
In-Reply-To: <87h7kl19qj.fsf@gnu.org>
Likely not worth combining this with ido then:-)
Tassilo Horn writes:
> "T.V Raman" <raman@google.com> writes:
>
> > I use ido and ido-completing-read+ and just tried this new package, was
> > But installing it from elpa and enabling it as documented made no
> > perceptible difference in the minibuffer with commands like find-file,
>
> Indeed, it doesn't do anything when ido is enabled. The reason is that
> it only adds its manchinery if `minibuffer-completion-table' is non-nil
> which seemed to be the right thing to check that we read something
> completable from the minibuffer. With ido enabled, it is always nil, at
> least for `find-file' and `switch-to-buffer'.
>
> That said, I'm not sure if it would be a useful extension to enable
> together with ido. With ido, you already see (some) possible
> completions, and ido also doesn't complete with stock
> `minibuffer-complete' as `aggressive-completion-mode' does but it has
> its own `ido-complete' which also tracks state important for ido such as
> the current directory...
>
> Bye,
> Tassilo
--
♉Id: kg:/m/0285kf1 🦮♉
--
♉Id: kg:/m/0285kf1 🦮♉
next prev parent reply other threads:[~2021-04-05 14:21 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-03 7:53 [GNU ELPA] New package proposal: aggressive-completion.el Tassilo Horn
2021-04-03 8:37 ` Tassilo Horn
2021-04-03 9:11 ` Manuel Uberti
2021-04-03 9:42 ` Tassilo Horn
2021-04-03 10:14 ` Jean Louis
2021-04-03 11:17 ` Jean Louis
2021-04-03 10:07 ` Jean Louis
2021-04-03 9:36 ` Jean Louis
2021-04-03 10:03 ` Tassilo Horn
2021-04-03 10:19 ` Jean Louis
2021-04-03 10:24 ` Tassilo Horn
2021-04-04 13:53 ` Basil L. Contovounesios
2021-04-04 19:05 ` Tassilo Horn
2021-04-04 20:12 ` T.V Raman
2021-04-05 7:01 ` Tassilo Horn
2021-04-05 14:21 ` T.V Raman [this message]
2021-04-04 20:26 ` Stefan Monnier
2021-04-05 7:17 ` Tassilo Horn
2021-04-03 9:49 ` Jean Louis
2021-04-03 10:05 ` Tassilo Horn
2021-04-03 11:53 ` Philip Kaludercic
2021-04-03 11:55 ` Philip Kaludercic
2021-04-03 13:43 ` Tassilo Horn
2021-04-03 17:22 ` [GNU ELPA] New package proposal: aggressive-completion.El Philip Kaludercic
2021-04-03 18:03 ` Tassilo Horn
2021-04-03 14:04 ` [GNU ELPA] New package proposal: aggressive-completion.el Stefan Monnier
2021-04-03 18:29 ` Tassilo Horn
2021-04-03 19:30 ` Tassilo Horn
2021-04-03 21:01 ` Stefan Monnier
2021-04-03 20:02 ` Gabriel
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=24683.7404.791668.929210@retriever.mtv.corp.google.com \
--to=raman@google.com \
--cc=emacs-devel@gnu.org \
--cc=tsdh@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 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).