From: "Bart Schaefer" <schaefer@candle.brasslantern.com>
To: zsh-workers@sunsite.auc.dk
Cc: Vincent Lefevre <vincent@vinc17.org>
Subject: Re: PATCH: Re: blah*[TAB] (difference between 3.1.6 and 3.1.9)
Date: Tue, 6 Jun 2000 15:57:25 +0000 [thread overview]
Message-ID: <1000606155725.ZM594@candle.brasslantern.com> (raw)
In-Reply-To: <200006061258.OAA09450@beta.informatik.hu-berlin.de>
On Jun 6, 2:58pm, Sven Wischnowsky wrote:
} Subject: PATCH: Re: blah*[TAB] (difference between 3.1.6 and 3.1.9)
}
} > > bindkey '\t' complete-word
} > > autoload -U compinit
} > > compinit
} > > zstyle ':completion:*' completer _expand _complete
} > > zstyle ':completion:*:expand:::' glob 1
} > > zstyle ':completion:*:expand:::' substitute 1
}
} And to get nearer to the expand-or-complete behaviour, you should also
} use:
}
} zstyle ':completion:*:expand:*' tag-order all-expansions
}
} That will make it insert only all the expansions in the line, not
} allowing you to menu between the original string, the expansions
} one-by-one and all expansions at once.
Eh? I just tried (again) my sequence in `zsh-3.1.9 -f' and I don't get
offered a menu. I just get the expansion inserted. I get exactly the
same behavior with your tag-order style as without.
And if your tag-order were going to matter, shouldn't it need to be:
zstyle ':completion:*:expand:*' tag-order - all-expansions
because
If any string in the value consists of only a hyphen, then
*only* the tags specified by the other strings in the value
are generated. Normally all tags not explicitly selected are
tried last if the specified tags fail to generate any
matches. This means that a value consisting only of a single
hyphen turns off completion.
} The _expand completer offers you the expansion of $ZSH_V (an empty
} string) and the original and enters menu-completion so that you can
} toggle between the two (with the `expansion' being inserted in the
} line immediately).
}
} Hm, maybe we shouldn't use `empty' expansions.
That would be consistent with previous version's behavior and with the
behavior of expand-or-complete.
--
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-06 15:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-06-06 12:58 Sven Wischnowsky
2000-06-06 15:57 ` Bart Schaefer [this message]
2000-06-06 16:44 ` Bart Schaefer
2000-06-08 7:18 Sven Wischnowsky
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=1000606155725.ZM594@candle.brasslantern.com \
--to=schaefer@candle.brasslantern.com \
--cc=vincent@vinc17.org \
--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).