From: "Bart Schaefer" <schaefer@candle.brasslantern.com>
To: Andy Spiegl <zsh.Andy@spiegl.de>,
ZSH User List <zsh-users@sunsite.auc.dk>
Subject: Re: completing from history
Date: Sat, 17 Jun 2000 03:05:52 +0000 [thread overview]
Message-ID: <1000617030552.ZM4725@candle.brasslantern.com> (raw)
In-Reply-To: <20000617040821.A4182@br-online.de>
On Jun 17, 4:08am, Andy Spiegl wrote:
} Subject: completing from history
}
} On Adam Spier's zsh page (http://www.new.ox.ac.uk/~adam/computing/zsh/) I
} found these lines in his .zsh
} # {{{ Simulate my old dabbrev-expand 3.0.5 patch
} zstyle ':completion:*:history-words' stop 'verbose'
} zstyle ':completion:*:history-words' remove_all_dups 'yep'
} # }}}
}
} But I must admit that I don't understand what I can do with it.
If you've got 3.1.9 installed, you can type <ESC /> or <ESC ,> to invoke
the _history-complete-older or _history-complete-newer bindings. The
above styles control whether the search cycles through the history and
whether it ever offers duplicate words -- except that it should be
`remove-all-dups' with hyphens, not underscores, and the value `yep'
does not work, it has to be `yes' `true' `1' or `on'. So Adam must not
be using the distributed version of _history_complete_word.
Oh, you do need to have run "compinit" to enable those bindings.
You can also add _history to your completer style like this:
zstyle ':completion:*' completer _complete _history
to have the history searched when you hit TAB and regular completion does
not find anything. (Or put it in front of _complete to have the history
tried first, but that's probably not what you want.)
--
Bart Schaefer Brass Lantern Enterprises
http://www.well.com/user/barts http://www.brasslantern.com
Zsh: http://www.zsh.org | PHPerl Project: http://phperl.sourceforge.net
next prev parent reply other threads:[~2000-06-17 3:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-06-17 2:08 Andy Spiegl
2000-06-17 3:05 ` Bart Schaefer [this message]
2000-06-17 10:52 ` Adam Spiers
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=1000617030552.ZM4725@candle.brasslantern.com \
--to=schaefer@candle.brasslantern.com \
--cc=zsh-users@sunsite.auc.dk \
--cc=zsh.Andy@spiegl.de \
/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).