Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: Unexpected foo==bar errors
- X-seq: zsh-workers 37919
- From: Mikael Magnusson <mikachu@xxxxxxxxx>
- To: Bart Schaefer <schaefer@xxxxxxxxxxxxxxxx>
- Subject: Re: Unexpected foo==bar errors
- Date: Mon, 8 Feb 2016 20:16:58 +0100
- Cc: zsh workers <zsh-workers@xxxxxxx>
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=JKPQm+IEMAz5ZrQcaD70L0RkkDiA0CK3rTQMHbvbxco=; b=xgELrqM8Tq4q8pS5xX2mXK0ToMRpE317OqWeRBe6xGyuzXIqnnwaHIrFSUS8Tc7A9p rkzjGoDt6zFSwP4DTXz+Jh0gnNBcC4bpgp5RRVJFnrWIhQ0E1YRaxsA3uSaRehVFUBWk LerY0+yeVY2Sn70SC52LC2ibm1DETFoBKFY5po0rfjmSVRqBe+WVXuNl+LQipRuhiJm8 TkedDsgcJFEWtzzu2eKewNYMZQomYk9oRFzryw2+l/9twoJzMKcI2OE0usGf+WHl1xhH sRvqQcUDO64Qv6cmHPzxTnjVZwijNQIziLOo2T7vo+L643wbqIhZtgQcOGlPC7W2UKWs 2WWw==
- In-reply-to: <160208104528.ZM12107@torch.brasslantern.com>
- List-help: <mailto:zsh-workers-help@zsh.org>
- List-id: Zsh Workers List <zsh-workers.zsh.org>
- List-post: <mailto:zsh-workers@zsh.org>
- Mailing-list: contact zsh-workers-help@xxxxxxx; run by ezmlm
- References: <CAHYJk3QRVQ893fMP+4CmdapK10vx5gP581pY358KSQdR1-sZuQ@mail.gmail.com> <160207111638.ZM30626@torch.brasslantern.com> <CAHYJk3S-Vj24041msXn6f8w3DM1pbv2uooxHUF3F=Ou8od_PxQ@mail.gmail.com> <160208104528.ZM12107@torch.brasslantern.com>
On Mon, Feb 8, 2016 at 7:45 PM, Bart Schaefer <schaefer@xxxxxxxxxxxxxxxx> wrote:
> On Feb 8, 4:52am, Mikael Magnusson wrote:
> } > The only use of $tf as far as I can see is to do lookups in the cache.
> }
> } Presumably at some point the given filename has to be interpreted so
> } that it can give any completions at all, even if it's not cached?
>
> On closer inspection yes, I'm wrong about this, $tf is passed to "tar -tf"
> to list the contents of the tar file even if not found in the cache.
>
> } I wonder if there's anywhere in the completion system that depends on
> } EQUALS being set... But maybe we should just 2> /dev/null the
> } assignment since tilde expansion also prints errors. (_zattr and _zip
> } also have this issue, presumably there are other places as well).
>
> Redirecting error would still leave $tf empty. But there's no way to
> cause process substitution [that is, <(...) >(...) and =(...) syntax]
> to be applied to the result of parameter expansion, except by using
> "eval" -- and of course globbing won't happen without GLOB_ASSIGN, so
> the only reason for tf=${~words[3]} (and the other assignments in _tar
> from lines 66-82) is to do tilde and equals expansion.
Well, considering that something simple as foo*.tar (expanding only to
one file) also leaves $tf empty, I'd say it's better to leave $tf
empty for any weird command substitutions as well, but suppress the
error messages.
--
Mikael Magnusson
Messages sorted by:
Reverse Date,
Date,
Thread,
Author