zsh-users
 help / color / mirror / code / Atom feed
From: John Cooper <john.cooper@eu.citrix.com>
To: Peter Stephenson <pws@csr.com>
Cc: zsh-users@sunsite.dk
Subject: Re: Completing strings from history?
Date: 26 Mar 2001 16:52:10 +0100	[thread overview]
Message-ID: <m366gwh6j9.fsf@kontiki.cam.eu.citrix.com> (raw)
In-Reply-To: <Tc0a88d01528802e6d5@mailsweeper01.cambridgesiliconradio.com>

Peter Stephenson <pws@csr.com> writes:

 > > Typing `foo<ESC-/>' (bound to _history-complete-older) finds the most recent
 > > word in the history beginning "foo".  Typing <ESC-/> again appears to do
 > > nothing.
 > > 
 > > Is it possible to set things up so that repeatedly typing <ESC-/> cycles back
 > > through all matches in the history?  (ala Emacs' dabbrev-expand)
 > 
 > You can do this by setting the `stop' style, which is so called because it
 > stops when it has reached as far back into the history as it can (unlike
 > normal menu completion which would continue cycling).
 > 
 >   zstyle ':completion:history-words:*' stop 1

Ideally, I'd prefer <ESC-/> to cycle back through the history _and_ have it
cycle round after reaching the end of the history.  Is this possible?

With the above zstyle, I find that hitting <ESC-/> after having reached the
oldest history item prohibits <ESC-,> from taking my forwards again, and
similarly, hitting <ESC-,> after cycling forwards to the most recent item
prohibits <ESC-/> from taking me backwards again.

Two more questions:

1. Is it possible to turn off the beep that's emitted every time I type <ESC-/>?

2. Can all matching words be displayed as per normal completions (then I'd see
   whether it's worth continuing to bang on <ESC-/> a few more times)?

Thanks again,

    --- John


  parent reply	other threads:[~2001-03-26 15:44 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-03-26 14:20 John Cooper
2001-03-26 14:34 ` Peter Stephenson
2001-03-26 15:25   ` Adam Spiers
2001-03-26 15:52   ` John Cooper [this message]
2001-03-26 16:47     ` Adam Spiers
2001-03-26 16:19   ` Bart Schaefer

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=m366gwh6j9.fsf@kontiki.cam.eu.citrix.com \
    --to=john.cooper@eu.citrix.com \
    --cc=pws@csr.com \
    --cc=zsh-users@sunsite.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).