From: Oliver Kiddle <okiddle@yahoo.co.uk>
To: zsh-workers@zsh.org
Subject: Re: [PATCH v2] Re: [PATCH] _add-zle-hook-widget: New completion.
Date: Fri, 22 Jul 2016 20:45:40 +0200 [thread overview]
Message-ID: <87043.1469213140@hydra.kiddle.eu> (raw)
In-Reply-To: <20160722062259.GB3457@tarsus.local2>
Daniel Shahaf wrote:
> > Furthermore, while checking that this wasn't intentional I noticed
> > a couple of functions that use _normal where _default was meant.
>
> _default appears to be undocumented.
Actually it sort of is documented: the section on special contexts which
mentions -default- and says that default implementations exist named
_context. Should there perhaps be findex entries there for each context?
Thinking about it, perhaps the original intention was that _dispatch
should be used but direct calls to _default are widespread and date
back to early times. How about the following.
Oliver
diff --git a/Doc/Zsh/compsys.yo b/Doc/Zsh/compsys.yo
index 8792324..460cbb6 100644
--- a/Doc/Zsh/compsys.yo
+++ b/Doc/Zsh/compsys.yo
@@ -4217,6 +4217,12 @@ This function completes words that are valid at command position: names of
aliases, builtins, hashed commands, functions, and so on. With the tt(-e)
flag, only hashed commands are completed. The tt(-) flag is ignored.
)
+findex(_default)
+item(tt(_default))(
+This function corresponds to the tt(-default-) special context. It is
+also used directly as a fallback when a function is unable to provide
+more specific completions.
+)
findex(_describe)
redef(SPACES)(0)(tt(ifztexi(NOTRANS(@ @ @ @ @ @ @ @ @ @ ))ifnztexi( )))
xitem(tt(_describe )[tt(-12JVx)] [ tt(-oO) | tt(-t) var(tag) ] var(descr) var(name1) [ var(name2) ] [ var(opt) ... ])
next prev parent reply other threads:[~2016-07-22 19:16 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-04 10:40 Next release (5.3) Peter Stephenson
2016-07-04 15:04 ` Bart Schaefer
2016-07-05 6:00 ` Sebastian Gniazdowski
2016-07-05 6:33 ` Bart Schaefer
2016-07-05 8:33 ` Peter Stephenson
2016-07-05 11:48 ` Peter Stephenson
2016-07-05 16:29 ` Bart Schaefer
2016-07-07 2:00 ` Daniel Shahaf
2016-07-13 5:00 ` add-zle-hook-widget " Daniel Shahaf
2016-07-14 0:11 ` Bart Schaefer
2016-07-17 1:51 ` Bart Schaefer
2016-07-17 15:00 ` [PATCH] _add-zle-hook-widget: New completion Daniel Shahaf
2016-07-17 19:21 ` Bart Schaefer
2016-07-17 20:40 ` Bart Schaefer
2016-07-17 21:57 ` Bart Schaefer
2016-07-18 9:47 ` Oliver Kiddle
2016-07-18 15:30 ` Bart Schaefer
2016-07-19 10:30 ` Oliver Kiddle
2016-07-19 17:58 ` Bart Schaefer
2016-07-20 6:54 ` [PATCH v2] " Daniel Shahaf
2016-07-21 15:28 ` Oliver Kiddle
2016-07-22 6:22 ` Daniel Shahaf
2016-07-22 18:21 ` Bart Schaefer
2016-07-22 18:45 ` Oliver Kiddle [this message]
2016-07-23 18:03 ` Daniel Shahaf
2016-07-17 14:59 ` add-zle-hook-widget Re: Next release (5.3) Daniel Shahaf
2016-07-17 18:48 ` Bart Schaefer
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=87043.1469213140@hydra.kiddle.eu \
--to=okiddle@yahoo.co.uk \
--cc=zsh-workers@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).