From: dana <dana@dana.is>
To: Chris Nebel <c.nebel@mac.com>
Cc: zsh-users <zsh-users@zsh.org>
Subject: Re: Fake parameter completion?
Date: Fri, 18 Oct 2019 18:44:24 -0500 [thread overview]
Message-ID: <3D4F79EC-3BFD-4966-99B8-F67BF5CFD8F1@dana.is> (raw)
In-Reply-To: <7C2ECA3E-EA6B-4C31-BF3A-1CF791F71785@mac.com>
On 18 Oct 2019, at 16:08, Chris Nebel <c.nebel@mac.com> wrote:
> 1. Why are “fake” and “fake-parameters” distinct styles? Obviously they
> behave differently in practice, but why couldn’t “fake” take the position
> into account and add the magic “=“ like “fake-parameters” does?
The immediate reason they work differently is that the styles are applied at
different points during completion. fake and fake-always are handled by the
low-level function _description, whilst fake-files and fake-parameters are
handled by their respective higher-level functions directly.
It probably could have been designed differently, but doing it this way seems
(comparatively) straight-forward, especially since they use incompatible
syntaxes for their values. But this was all long before my time, so i'm just
speculating
On 18 Oct 2019, at 16:08, Chris Nebel <c.nebel@mac.com> wrote:
> 2. What is the actual value of the “*” in the context? Not “parameters”,
> apparently. (I should mention that I do not truly understand zshcompsys.)
The tag used for parameter completion is parameters, but _parameters omits it
when it looks up the style. I confess i'm not sure what the significance of
that is
dana
prev parent reply other threads:[~2019-10-18 23:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-18 21:08 Chris Nebel
2019-10-18 23:44 ` dana [this message]
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=3D4F79EC-3BFD-4966-99B8-F67BF5CFD8F1@dana.is \
--to=dana@dana.is \
--cc=c.nebel@mac.com \
--cc=zsh-users@zsh.org \
/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).