Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: compset -q oddities
- X-seq: zsh-workers 39340
- From: Daniel Shahaf <d.s@xxxxxxxxxxxxxxxxxx>
- To: zsh-workers@xxxxxxx
- Subject: Re: compset -q oddities
- Date: Thu, 15 Sep 2016 05:10:38 +0000
- Dkim-signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= daniel.shahaf.name; h=content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-sasl-enc :x-sasl-enc; s=mesmtp; bh=gBu87FqvJDpxvaiUdnOEHZc51AU=; b=ohFXKA mWd/7DjjiQRXt6DM6Y8x8teG3ai5gyagKowdSnNrK16l3P8uyFK+Pm4hAk3geD7D jn9i6wF/C01RJyGwYZXxl7hYvHWydapaRJaAxeuxTBlof12kdphXRpARcouOLFR9 /iNUX0uVJVXPcnhvPFjrXoznzDQq7q85g2YrE=
- Dkim-signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-sasl-enc :x-sasl-enc; s=smtpout; bh=gBu87FqvJDpxvaiUdnOEHZc51AU=; b=LdpgH t1Wdq1zYXiqXAVbPGzDL9DU1EPYuc1g215z8IXvLt1U6JmMjeUVO/jBtufkpNtED SFbnAkdmZa6F9kB6QETbv3oIaAUwtGKjEVy7ZhaUsHMzGGhUSjg+R65waIXHjD/7 b8V6YgN82s7uxzEChTw0Dz6g/MoiY3zIBan9BI=
- In-reply-to: <160914105654.ZM29879@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: <20160911073031.GA19137@fujitsu.shahaf.local2> <160911191422.ZM21970@torch.brasslantern.com> <20160912230632.GA29577@fujitsu.shahaf.local2> <CGME20160913063712eucas1p2deca64bf6437fe218152a2ced73328a4@eucas1p2.samsung.com> <160912232853.ZM27002@torch.brasslantern.com> <20160913112141.1243fbde@pwslap01u.europe.root.pri> <160914105654.ZM29879@torch.brasslantern.com>
Bart Schaefer wrote on Wed, Sep 14, 2016 at 10:56:54 -0700:
> On Sep 13, 11:21am, Peter Stephenson wrote:
> }
> } However, I'm not sure we want to fiddle with this before a release which
> } we really ought to be making imminently as this is just one of a series
> } of incrementally partially fixed problems in this area
>
> I concur, we can e.g. note these issues in README or somewhere ("the
> calling completer may need to test [[ -n $words[CURRENT] ]] before
> using `compset -q'" or similar verbiage) and move on for now.
I'd write that docs patch but I don't understand what it should say?
Messages sorted by:
Reverse Date,
Date,
Thread,
Author