Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: Completion behavior change in 3.0-pre3
- X-seq: zsh-workers 1682
- From: "Bart Schaefer" <schaefer@xxxxxxxxxxxxxxxxxxxxxxx>
- To: "C. v. Stuckrad" <stucki@xxxxxxxxxxxxxxxxx>
- Subject: Re: Completion behavior change in 3.0-pre3
- Date: Wed, 17 Jul 1996 08:29:45 -0700
- Cc: zsh-workers@xxxxxxxxxxxxxxx
- In-reply-to: Christoph von Stuckrad <stucki@xxxxxxxxxxxxxxxxx> "Re: Completion behavior change in 3.0-pre3" (Jul 17, 11:52am)
- References: <Pine.GSO.3.94.960717103629.21831A-100000@petzval>
- Reply-to: schaefer@xxxxxxx
On Jul 17, 11:52am, Christoph von Stuckrad wrote:
> Subject: Re: Completion behavior change in 3.0-pre3
> On Mon, 15 Jul 1996, Bart Schaefer wrote:
>
> > Here's zsh 3.0-pre3:
> >
> > zagzig<3> echo z*i<TAB>
> > (feep)
> > zagzig<3> echo z\*i
>
> Isn't this a feature instead of a bug ?
Given that Zoltan didn't mention this as an intentional change, I don't
think it's meant to be a feature.
> THIS 'z\*i' is exactly what would be used on the input line if the
> pattern doesn't glob
I *might* agree if I had GLOB_COMPLETE set; but I don't, so it
should be waiting for me to make the pattern unambiguous before it
decides that it has to quote anything. Even with GLOB_COMPLETE,
I can't really go along with you; performing completion/expansion
shouldn't change the *semantics* of the command line:
touch z*i # Fails with "no match"
touch z\*i # Creates a new file
In effect, zsh should never rewrite the line when it (feep)s, only
when it successfully expands or completes something.
> So if this behaviour depends on 'nonomatch' I would appreciate it!
I don't have nonomatch set either. (Gad, that sounds illiterate.
A triple negative? Anyway, it doesn't depend on nonomatch.)
> If not, well, I think one can get used to it.
Get used to backing up to remove quoting from every glob pattern on the
line after every completion? Or get used to not using completion?
Messages sorted by:
Reverse Date,
Date,
Thread,
Author