From: Sven Wischnowsky <wischnow@informatik.hu-berlin.de>
To: zsh-workers@sunsite.auc.dk
Subject: Re: completing history words
Date: Wed, 5 Jul 2000 16:36:44 +0200 (MET DST) [thread overview]
Message-ID: <200007051436.QAA11795@beta.informatik.hu-berlin.de> (raw)
In-Reply-To: Oliver Kiddle's message of Wed, 05 Jul 2000 15:10:10 +0100
Oliver Kiddle wrote:
> I'm a little bit mystified by the way _history_complete_word is
> implemented as it seems to re-implement menu-completion while not
> offering non-menu completion. Why does it not just complete history
> words and rely on separate completers based on different builtin
> widgets (menu-complete, complete-word etc)? I wanted to be able to
> complete history in a fairly normal way but it behaves in a slightly
> strange way, doing things like inserting a match for ambiguous
> completions.
It's rather old...
> I created a small function (_complete_history) containing just the
> line:
> compadd -Q -a 'historywords[2,-1]'
Have you seen the _history completer?
> ...
>
>
> It actually seems to have a problem with strange characters (e.g.
> '$') not being considered part of the word being completed but other
> than that, it is fine.
See some recent mails, _history and _h_c_w put $IPREFIX into $PREFIX
for that.
> Obviously, my _complete_history function could be much improved with
> styles for sorting and to manipulate compstate so listing etc can be
> turned off but this way of doing it seems better to me. It is much
> simpler and configuration of it will be more similar to configuring for
> other completion widgets. Can anyone please explain why it is currently
> done differently?
Well, Adam will have to have the final word about this...
Bye
Sven
--
Sven Wischnowsky wischnow@informatik.hu-berlin.de
next reply other threads:[~2000-07-05 14:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-07-05 14:36 Sven Wischnowsky [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-07-05 14:10 Oliver Kiddle
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=200007051436.QAA11795@beta.informatik.hu-berlin.de \
--to=wischnow@informatik.hu-berlin.de \
--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).