zsh-users
 help / color / mirror / code / Atom feed
From: "Bart Schaefer" <schaefer@candle.brasslantern.com>
To: <zsh-users@sunsite.auc.dk>
Subject: Re: glob completion without menu style completion
Date: Fri, 15 Sep 2000 11:55:39 -0700	[thread overview]
Message-ID: <000915115539.ZM17342@candle.brasslantern.com> (raw)
In-Reply-To: <000101c01f3e$cf699350$21c9ca95@mow.siemens.ru>

On Sep 15, 10:00pm, Andrej Borsenkow wrote:
> Subject: RE: glob completion without menu style completion
> >
> > If I don't have setopt glob_complete and I do
> >
> > rmdir *TAB
> >
> > the * gets replaced with all files in the directory that would be
> > matched by * if I were to just hit return at that moment.
> >
> > Is there a way to get it so that when I type
> >
> > rmdir *TAB
> >
> > the * gets replaced with all the choices that the completion system
> > returns at that time
> 
> Yes, I can reproduce it. It happens, because by default TAB is bound to
> expand-or-complete widget that tries expansion if it sees glob pattern
> *before* it tries completion. So, it seems, that completion system sees
> input line with already expanded '*' ... I personally consider it a bug,
> but Sven should answer it when he is back.

It's not a bug, it's the defined behavior of expand-or-complete.

> You are better off if you redefine TAB to simple expand-word like
> 
> bindkey '^I' expand-word

You mean "complete-word", not "expand-word".  And if you run "compinit"
*after* setting your styles with zstyle, *and* you have used the _expand
completer, then compinit rebinds TAB to complete-word for you, for just
this reason.

> In general, it is always good idea to use plain complete-word with new
> completion system, because then you have much better control over possible
> interpretation of patterns.

Exactly.


  reply	other threads:[~2000-09-15 18:59 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-09-15 17:30 E. Jay Berkenbilt
2000-09-15 18:00 ` Andrej Borsenkow
2000-09-15 18:55   ` Bart Schaefer [this message]
2000-09-15 19:52     ` E. Jay Berkenbilt
2000-09-18  7:05     ` Andrej Borsenkow
2000-09-15 18:59   ` E. Jay Berkenbilt

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=000915115539.ZM17342@candle.brasslantern.com \
    --to=schaefer@candle.brasslantern.com \
    --cc=zsh-users@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).