From: "Bart Schaefer" <schaefer@candle.brasslantern.com>
To: zsh-workers@sunsite.auc.dk
Subject: Re: PATCH: 3.1.6-pws-11: Completion suggestions + fixes + sorting tags
Date: Wed, 15 Dec 1999 18:35:32 +0000 [thread overview]
Message-ID: <991215183532.ZM15333@candle.brasslantern.com> (raw)
In-Reply-To: <199912150909.KAA04890@beta.informatik.hu-berlin.de>
On Dec 15, 10:09am, Sven Wischnowsky wrote:
} Subject: Re: PATCH: 3.1.6-pws-11: Completion suggestions + fixes + sorting
}
} Peter Stephenson wrote:
}
} > 2. I don't really like the way ZLS_COLORS is sidelined. There doesn't seem
} > to be any point in it if you're using new completion. Perhaps if it's
} > set when completion is initialised it could be set to the default for
} > the list-colors style.
}
} Hm, my bad English shows... There doesn't seem to be a point in what?
There doesn't seem to be a reason to have a ZLS_COLORS parameter at all.
} > 6. Incremental completion may be missing a few things, for example
} > a way of switching it off after it's completed a word with tab, it
} > annoys me that it doesn't, and an option to complete unambiguous bits
} > automatically. The function doesn't seem to be described anywhere, but
} > I think someone already suggested the zle functions needed their own
} > manual entry.
}
} Incremental completion is a hack, yes. Have you had a look at
} predict-on lately? It can do completion, too, nowadays.
incremental-complete-word is somewhat vi-like (modal) even though editing
within it is emacs-like. predict-on is more like an emacs minor mode.
I haven't ever tried combining predict-on with menu-select ...
BTW, predict-on is still using _style as well. Is this the correct fix?
Index: Functions/Zle/predict-on
===================================================================
@@ -61,7 +61,7 @@
# get out of that `case'.
repeat 1
do
- _style -s '' cursor crs
+ zstyle -s ":completion${curcontext}" cursor crs
case $crs in
(complete)
# At the place where the completion left it, if it is after
@@ -119,7 +119,7 @@
then
compstate[list]=''
compstate[force_list]=yes
- elif _style '' list always ]]
+ elif zstyle ":completion${curcontext}:predict" list always ]]
then
compstate[force_list]=yes
fi
--
Bart Schaefer Brass Lantern Enterprises
http://www.well.com/user/barts http://www.brasslantern.com
next prev parent reply other threads:[~1999-12-15 18:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-12-15 9:09 Sven Wischnowsky
1999-12-15 18:35 ` Bart Schaefer [this message]
1999-12-15 20:31 ` Peter Stephenson
-- strict thread matches above, loose matches on Subject: below --
1999-12-16 8:34 Sven Wischnowsky
1999-12-16 8:28 Sven Wischnowsky
1999-12-14 21:56 Peter Stephenson
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=991215183532.ZM15333@candle.brasslantern.com \
--to=schaefer@candle.brasslantern.com \
--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).