Zsh Mailing List Archive
Messages sorted by:
Re: compset -q oddities
- X-seq: zsh-workers 39320
- From: Bart Schaefer <schaefer@xxxxxxxxxxxxxxxx>
- To: zsh-workers@xxxxxxx
- Subject: Re: compset -q oddities
- Date: Wed, 14 Sep 2016 07:59:46 -0700
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=brasslantern-com.20150623.gappssmtp.com; s=20150623; h=from:message-id:date:in-reply-to:comments:references:to:subject :mime-version; bh=2SquXSjB42zMO3IYKy9BcNBFLGhV5WGZGa3nVr0tLvA=; b=FBMAYOmey2LnEw1FbFcrPrNR/VTuKw5HPTS2TOyAPpSPTKXIynqXywy9gzuKR0nvWM YdJ3eVZaNlYkW23Xpucj57C6pr5hGj9JZsfobj6JaphntnC0YcWmY7D9jKh0WHQX4EVb QVPeXec8+6e8YULKatZUkdkRoubv3QymlCFS5UFgidAXsJbjEV/0OxCk7btYHFsy/8MQ UoyXvIvDcOHWEuzEhP47cQypqKGUBVkw9c1mEUIKhULyGfFhCRRBMlb79ChRZMeJO+6c Vo+5bbdKtx+ekYNJ5nWqRknSIoc3nXnvYXvo6ZMMu2yUqRYImJHbFskvsdHrGU7EFZm6 JOHA==
- In-reply-to: <20160914061252.GA22452@fujitsu.shahaf.local2>
- List-help: <mailto:firstname.lastname@example.org>
- List-id: Zsh Workers List <zsh-workers.zsh.org>
- List-post: <mailto:email@example.com>
- Mailing-list: contact zsh-workers-help@xxxxxxx; run by ezmlm
- References: <20160911073031.GA19137@fujitsu.shahaf.local2> <160911191422.ZM21970@torch.brasslantern.com> <20160912230632.GA29577@fujitsu.shahaf.local2> <160912232853.ZM27002@torch.brasslantern.com> <20160914032254.GA32528@fujitsu.shahaf.local2> <160913222029.ZM13117@torch.brasslantern.com> <20160914061252.GA22452@fujitsu.shahaf.local2>
On Sep 14, 6:12am, Daniel Shahaf wrote:
} Subject: Re: compset -q oddities
} Why should "f \\\~\\\~\\\~<TAB>" fail?
} Essentially, 'compset -q' "looks through" one level of quoting, and
} whatever is happening in the "ssh \git.code<TAB>" case looks through the
} second level of quoting.
} Makes sense?
Yes, except that in \g the backslash really is redundant, whereas with
\~ the intent might be to compare a literal tilde to an expansion tilde
(which is different still from a globbing tilde).
} Bart Schaefer wrote on Tue, Sep 13, 2016 at 22:20:29 -0700:
} > Also now that I think of it, there's only one match with that compadd,
} > so it should have appended a trailing space and the second tab should
} > have been in an entirely new (also empty) word.
} That's a bit tricky. I think it should append an escaped space, e.g.,
} "sh -c touc<TAB>" should append <h> <Backslash> <Space>.
No, that's *exactly* the kind of DWIM-ing that we abandoned. If the user
wants the space quoted, then he should start with "sh -c 'touc<TAB>".
Messages sorted by: