From: Sebastian Gniazdowski <sgniazdowski@gmail.com>
To: Eric Freese <ericdfreese@gmail.com>
Cc: Zsh Users <zsh-users@zsh.org>
Subject: Re: Anyone familiar with auto-fu.zsh project?
Date: Sat, 9 Jun 2018 17:30:38 +0200 [thread overview]
Message-ID: <CAKc7PVDe29JSCEeXU7F_dqG5a7TvfTz=sP3=4nDLOm1jQOxFnA@mail.gmail.com> (raw)
In-Reply-To: <CAAikoA+iGXVQXGfRP-RepefEc+FAG0+brAVcPjp5p=969+j7Kg@mail.gmail.com>
New autosuggestions is on the way (reddit says), it looks like the
capture-completion zpty-based solution worked?
On 6 June 2018 at 20:35, Eric Freese <ericdfreese@gmail.com> wrote:
> Check out https://github.com/Valodim/zsh-capture-completion.
>
> I referenced it recently to implement completion suggestions in
> zsh-autosuggestions:
> https://github.com/zsh-users/zsh-autosuggestions/pull/330
>
> On Wed, Jun 6, 2018 at 11:43 AM Sebastian Gniazdowski
> <sgniazdowski@gmail.com> wrote:
>>
>> Hello,
>> last commit to the project is from 2013 and I cannot get it up and
>> running. Is anyone familiar with its method of functioning? A friend
>> guesses it pretends <tab> key to be pressed after each character, is
>> that true? It would then mean it constantly shows completions under
>> prompt. Is using shell this way actually possible?
>>
>> In general, I'm looking for a method of calling completion functions
>> manually and presenting the results in different form. Does someone
>> know anything about this problem?
>>
>> --
>> Best regards,
>> Sebastian Gniazdowski
>
> --
> Sent from my iPhone
next prev parent reply other threads:[~2018-06-09 15:31 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-06 17:42 Sebastian Gniazdowski
2018-06-06 18:35 ` Eric Freese
2018-06-09 15:30 ` Sebastian Gniazdowski [this message]
2018-06-10 0:58 ` Eric Freese
2018-06-11 5:24 ` Sebastian Gniazdowski
2018-06-11 8:25 ` Eric Freese
2018-06-11 9:46 ` Sebastian Gniazdowski
2018-06-12 1:55 ` Eric Freese
2018-06-12 10:23 ` Sebastian Gniazdowski
2018-06-12 11:32 ` Peter Stephenson
2018-06-13 4:09 ` Eric Freese
2018-06-13 7:26 ` dana
2018-06-13 7:32 ` Sebastian Gniazdowski
2018-06-13 8:28 ` Sebastian Gniazdowski
2018-06-13 9:17 ` dana
2018-06-13 10:48 ` Sebastian Gniazdowski
2018-06-13 11:43 ` dana
2018-06-14 8:55 ` Peter Stephenson
2018-06-14 9:48 ` dana
2018-06-14 10:00 ` Peter Stephenson
2018-06-13 7:27 ` Sebastian Gniazdowski
2018-06-06 23:45 ` Takeshi Banse
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAKc7PVDe29JSCEeXU7F_dqG5a7TvfTz=sP3=4nDLOm1jQOxFnA@mail.gmail.com' \
--to=sgniazdowski@gmail.com \
--cc=ericdfreese@gmail.com \
--cc=zsh-users@zsh.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.vuxu.org/mirror/zsh/
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 NNTP newsgroup(s).