unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Juri Linkov <juri@linkov.net>
To: Ergus <spacibba@aol.com>
Cc: emacs-devel@gnu.org
Subject: Re: zsh-like zcomplete-mode based on icomplete-mode
Date: Sun, 10 Apr 2022 10:38:58 +0300	[thread overview]
Message-ID: <865ynh9yp1.fsf@mail.linkov.net> (raw)
In-Reply-To: <20220410010557.2l4zh5yasmanmk7z@Ergus> (Ergus's message of "Sun,  10 Apr 2022 03:05:57 +0200")

>>Here is the first version of the mode with the behavior like in zsh,
>>but that is based on icomplete-mode.  So many customizable variables
>>and commands were copied from icomplete-mode, but instead of displaying
>>completions as an overlay in the minibuffer, in zcomplete-mode
>>completions are displayed in the standard *Completions* window.
>>All other icomplete features are preserved in zcomplete, such as
>>typing in the minibuffer continuously updates a list of possible
>>completions that match the typed string:
>
> After the first completion I get this:
>
> minibuffer-next-completion: Wrong type argument: number-or-marker-p, nil
>
> And it stops working...
>
> SO I need something special?

I pushed a fix to master, please try again.



  reply	other threads:[~2022-04-10  7:38 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-09 18:45 zsh-like zcomplete-mode based on icomplete-mode Juri Linkov
2022-04-09 20:30 ` Tassilo Horn
2022-04-10  7:38   ` Juri Linkov
2022-04-10  9:12     ` Tassilo Horn
2022-04-10 16:31       ` [External] : " Drew Adams
2022-04-10 19:11       ` Juri Linkov
2022-04-10  1:05 ` Ergus
2022-04-10  7:38   ` Juri Linkov [this message]
2022-04-10 10:41     ` Ergus
2022-04-10 16:34       ` [External] : " Drew Adams
2022-04-10 19:16       ` Juri Linkov
2022-04-10 21:45         ` Ergus
2022-04-11 16:53           ` Juri Linkov
2022-04-12 17:15       ` Juri Linkov

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=865ynh9yp1.fsf@mail.linkov.net \
    --to=juri@linkov.net \
    --cc=emacs-devel@gnu.org \
    --cc=spacibba@aol.com \
    /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).