From: Adam Spiers <adam@thelonious.new.ox.ac.uk>
To: zsh-workers@sunsite.auc.dk
Subject: Re: Autocompletion ala windows-esque
Date: Wed, 29 Sep 1999 21:23:38 +0100 [thread overview]
Message-ID: <19990929212338.C16175@thelonious.new.ox.ac.uk> (raw)
In-Reply-To: <19990929191705Z13390-21686+194@scapa.cs.ualberta.ca>
Benjamin Korvemaker (benjamin@cs.ualberta.ca) wrote:
> Forgive me now for this horrible thought.
>
> I'm at that point in my life where I need a shell that fills in the
> completion automagically and changes it as necessary the more I type
> (just like that horrible feature that MS products tend to have). I'm
> crazy, I admit it. To make life easier in the future, I'm planning on
> putting potential completions into a list or array (of the zsh variety).
>
> Before I begin the nastiness, has someone already done this?
If I understand you correctly, then yes, there's a function called
incremental-complete-word, which has this near its start:
# This allows incremental completion of a word. After starting this
# command, a list of completion choices can be shown after every character
# you type, which you can delete with ^h or DEL. RET will accept the
# completion so far. You can hit TAB to do normal completion, ^g to
# abort back to the state when you started, and ^d to list the matches.
although it has a few things which I think could be improved upon
(this is next on my to-do list, in fact :-)
Presumably you'd want to tell it complete words from the history. I
don't know when it first appeared, but you're best off using it with
the latest development versions: 3.1.6 and later.
prev parent reply other threads:[~1999-09-30 2:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-09-29 19:16 Benjamin Korvemaker
1999-09-29 20:23 ` Adam Spiers [this message]
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=19990929212338.C16175@thelonious.new.ox.ac.uk \
--to=adam@thelonious.new.ox.ac.uk \
--cc=adam@spiers.net \
--cc=zsh-workers@sunsite.auc.dk \
/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).