zsh-workers
 help / color / mirror / code / Atom feed
From: Oliver Kiddle <okiddle@yahoo.co.uk>
To: Zsh workers <zsh-workers@sunsite.dk>
Cc: Andrew Pimlott <andrew@pimlott.net>
Subject: Re: Bug#236350: zsh: _prefix completer broken?
Date: Sat, 06 Mar 2004 19:03:02 +0100	[thread overview]
Message-ID: <4419.1078596182@trentino.logica.co.uk> (raw)
In-Reply-To: <1040306173839.ZM5329@candle.brasslantern.com>

Bart wrote:
> 
> The add-space style does default to true, and you're seeing exactly what
> you should be seeing.  What you (and possibly the documentation) missed
> is that the add-space style applies only to the _expand and _prefix
> completers, so its default setting makes no difference if you aren't
> using one of those.

I can reproduce:
% zsh -f
% autoload -U compinit; compinit
% setopt completeinword
% zstyle ':completion:*' completer _complete _prefix
% egre<tab>foo
 gives:
% egrepfoo
  with the cursor over the f.

So where's the space?
Now set: zstyle ':completion:*' add-space true
and try again. Is it perhaps just meant to be for _expand that
add-space defaults to true?

> In both 4.2.0-pre-3 and 4.0.7, my completion style looks like this:
> 
> zstyle ':completion:*' completer \
>   _oldlist _expand _complete _match _ignored _approximate _prefix
> 
> However, 4.2.0-pre-3 never gets beyond trying _approximate.  The output

This is the bug I reported in 17846.

For now, I moved _prefix before _approximate.

Oliver


  parent reply	other threads:[~2004-03-06 18:09 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <E1AzKUu-0003tz-00@techloaner2.idiomtech.com>
2004-03-06  1:35 ` Clint Adams
2004-03-06 16:05   ` Andrew Pimlott
2004-03-06 17:38     ` Bart Schaefer
2004-03-06 17:59       ` Bart Schaefer
2004-03-06 18:03       ` Oliver Kiddle [this message]
2004-03-06 23:32         ` Bart Schaefer
2004-03-08 10:41         ` 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=4419.1078596182@trentino.logica.co.uk \
    --to=okiddle@yahoo.co.uk \
    --cc=andrew@pimlott.net \
    --cc=zsh-workers@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).