unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Jean Louis <bugs@gnu.support>
To: Tassilo Horn <tsdh@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: [GNU ELPA] New package proposal: aggressive-completion.el
Date: Sat, 3 Apr 2021 12:36:18 +0300	[thread overview]
Message-ID: <YGg3EvFfNGq3rYWn@protected.localdomain> (raw)
In-Reply-To: <87o8evok58.fsf@gnu.org>

* Tassilo Horn <tsdh@gnu.org> [2021-04-03 11:19]:
> Hi all,
> 
> I'd like to propose the attached aggressive-completion.el as a new GNU
> ELPA package.  I've used this since several months and now had the time
> to extract it from my ~/.emacs and make a proper minor-mode out of it.
> 
> What is it?
> ===========
> 
> I've used several different minibuffer completion frameworks in the past
> (including ivy, raven, and selectrum) in the past but always came back
> to the standard emacs minibuffer completion with its nice configuration
> means in terms of `completion-category-overrides' and friends.
> 
> What I've liked with the other frameworks, however, was that the
> completion candidates are immediately visible and in many scenarios I
> needed less typing (especially less pinky-stressing TAB-ing).
> 
> So the central idea of aggressive-completion.el is that it
> 
>   1) automatically completes for you after a short delay, and it
>   2) always shows the completion help (unless there are too many).
> 
> Without further ado, here it is (comments welcome):

I wish to try it out. I recommend that you first do:

M-x checkdoc-buffer

as to follow conventions. I can also see these compiler errors.

aggressive-completion.el:50:1: Warning: defgroup for ‘aggressive-completion’
    fails to specify containing group
aggressive-completion.el:66:1: Warning: defcustom for
    ‘aggressive-completion-no-complete-commands’ fails to specify type
aggressive-completion.el:66:1: Warning: defcustom for
    ‘aggressive-completion-no-complete-commands’ fails to specify type

In aggressive-completion--setup:
aggressive-completion.el:134:24: Warning: reference to free variable
    ‘aggressive-completion-minibuffer-map’

In end of data:
aggressive-completion.el:155:35: Warning: the function
    ‘icomplete-fido-backward-updir’ is not known to be defined.



  parent reply	other threads:[~2021-04-03  9:36 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 [this message]
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
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=YGg3EvFfNGq3rYWn@protected.localdomain \
    --to=bugs@gnu.support \
    --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).