From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=-1.0 required=5.0 tests=DKIM_ADSP_CUSTOM_MED, FREEMAIL_FROM,MAILING_LIST_MULTI,RCVD_IN_DNSWL_NONE autolearn=ham autolearn_force=no version=3.4.4 Received: (qmail 28178 invoked from network); 1 Jun 2020 08:23:15 -0000 Received: from ns1.primenet.com.au (HELO primenet.com.au) (203.24.36.2) by inbox.vuxu.org with ESMTPUTF8; 1 Jun 2020 08:23:15 -0000 Received: (qmail 28412 invoked by alias); 1 Jun 2020 08:23:06 -0000 Mailing-List: contact zsh-users-help@zsh.org; run by ezmlm Precedence: bulk X-No-Archive: yes List-Id: Zsh Users List List-Post: List-Help: List-Unsubscribe: X-Seq: 24890 Received: (qmail 16242 invoked by uid 1010); 1 Jun 2020 08:23:06 -0000 X-Qmail-Scanner-Diagnostics: from mail-il1-f179.google.com by f.primenet.com.au (envelope-from , uid 7791) with qmail-scanner-2.11 (clamdscan: 0.102.3/25828. spamassassin: 3.4.4. Clear:RC:0(209.85.166.179):SA:0(-2.0/5.0):. Processed in 4.588888 secs); 01 Jun 2020 08:23:06 -0000 X-Envelope-From: roman.perepelitsa@gmail.com X-Qmail-Scanner-Mime-Attachments: | X-Qmail-Scanner-Zip-Files: | Received-SPF: pass (ns1.primenet.com.au: SPF record at _netblocks.google.com designates 209.85.166.179 as permitted sender) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=NtMInjuiM74TgVpejuEBfu8NPnQzhDSYYQ6wBsloUS4=; b=KWYki2ah3PLLtNHVRZ47YhdPmj7efmnwoc+6poZT0IQ3JJdM9hP5MGcg7nWc3guU2L q4Gk5I3eJ+vKX8RAalpBkvqHYStqbFGBAkBpvTYoZPZ99yvv+8DJ+xqV3hCk8EedUlYc 2c5vsluV8en1P7kbWgrzTbN0PziCVfM7TH9LKttJsy1voSTzQccBjtNeZ2396DdnDyCx 83dde4/s4FJ7CYBvd38u/YsvabPlAhOVXuV73Jz3GU1RbB9fyZt0IvsfBIJgVtkrU4kn G6tdr/bCQlS3q/DLwc3IPL1OWdH+JDfbpntFqS5c9skZnXc+G8GYPeMnmW87VjQ+O3nz 5BaQ== X-Gm-Message-State: AOAM533EM0Vtk6EUxIw1Kp157G4X93Pyzsor3SZmNYLddosC61iCF1BV 3dJtqs1vtcQ7H9c0kFcL0w2eIvbYnebA7j8r5w4x6b5AP00= X-Google-Smtp-Source: ABdhPJxeZu8eIXLXfPqHjqVuEDOQZbaahf5R+MQdzlzGsJxvKl5uszZhjGg4HuUivrx3Q3Jhv8XA4B3ShZ1sh0gXZKY= X-Received: by 2002:a05:6e02:584:: with SMTP id c4mr15603904ils.304.1590999748150; Mon, 01 Jun 2020 01:22:28 -0700 (PDT) MIME-Version: 1.0 References: <20200601080730.7d373c99@tarpaulin.shahaf.local2> In-Reply-To: <20200601080730.7d373c99@tarpaulin.shahaf.local2> From: Roman Perepelitsa Date: Mon, 1 Jun 2020 10:22:17 +0200 Message-ID: Subject: Re: Completion introspection To: Daniel Shahaf Cc: Zsh Users Content-Type: text/plain; charset="UTF-8" On Mon, Jun 1, 2020 at 10:07 AM Daniel Shahaf wrote: > > What problem are you trying to solve? In addition to regular tab completion (expand-or-complete) I have another key binding for file completion with fzf. If I complete `vi ./` with tab, it'll ask me to choose the first path segment. If I complete it with alt-i (my fzf file completion binding), I'll be presented with fuzzy search UI over all files in the current directory (recursively). Unfortunately, alt-i binding doesn't work very well. It tries to guess which word is being completed and which command but it does it without involving the standard zsh completion system, so it fails often. I'm trying to improve it. Maybe there is another way? Perhaps it's possible to configure zsh completion system so that all file completions are recursive? My tab binding is actually also using fzf if there are multiple possible completions, so if file completions were recursive, that would work. > Why must the widget not be a completion widget? I'm not sure if it must be. The current widget isn't a completion widget and I know how to fix it if only I knew how to get the bits of information I asked about (the word that would be completed if I pressed tab, etc.). Roman.