zsh-workers
 help / color / mirror / code / Atom feed
From: Sven Wischnowsky <wischnow@informatik.hu-berlin.de>
To: zsh-workers@sunsite.auc.dk
Subject: RE: PATCH: Re: ignored-patterns giving correction a go
Date: Mon, 20 Mar 2000 11:54:33 +0100 (MET)	[thread overview]
Message-ID: <200003201054.LAA10458@beta.informatik.hu-berlin.de> (raw)
In-Reply-To: "Andrej Borsenkow"'s message of Mon, 20 Mar 2000 13:50:30 +0300


Andrej Borsenkow wrote:

> > > The point being that perhaps it should not be bound to a key by compinit
> > > if it's not in the completer list by default ...
> > 
> > Ah, right. The patch does that (I think this is saver than changing
> > the default completer value).
> > 
> 
> Looks like you forgot to include it ...

Ahem.

Bye
 Sven

diff -ru ../z.old/Completion/Commands/_next_tags Completion/Commands/_next_tags
--- ../z.old/Completion/Commands/_next_tags	Mon Mar 20 11:07:24 2000
+++ Completion/Commands/_next_tags	Mon Mar 20 11:32:04 2000
@@ -1,4 +1,13 @@
-#compdef -k complete-word \C-xn
+#autoload
+
+# To use this, put _next_tags at the beginning of the completer style,
+# define it as a completion widget and bind it to a key, e.g.:
+#
+#  zle -C _next_tags complete-word _next_tags
+#  bindkey '^Xn' _next_tags
+#
+# Makes it be bound to ^Xn.
+
 
 # Main widget/completer.
 
diff -ru ../z.old/Doc/Zsh/compsys.yo Doc/Zsh/compsys.yo
--- ../z.old/Doc/Zsh/compsys.yo	Mon Mar 20 11:07:07 2000
+++ Doc/Zsh/compsys.yo	Mon Mar 20 11:34:00 2000
@@ -1867,8 +1867,8 @@
 var(N), complete the var(N)th most recently modified file.  Note the
 completion, if any, is always unique.
 )
-findex(_next_tags (^Xn))
-item(tt(_next_tags (^Xn)))(
+findex(_next_tags)
+item(tt(_next_tags))(
 This allows to complete types of matches that are not immediately
 offered because of the setting of the tt(tag-order) style. After a
 normal completion was tried, invoking this command makes the matches
@@ -1878,6 +1878,12 @@
 contain tt(_next_tags) as its first string. With that, the normal key
 binding (normally tt(TAB)) can be used to complete the matches shown
 after the call to tt(_next_tags).
+
+Normally, this command is not bound to a key. To invoke it with, say
+`tt(^Xn)', one would use:
+
+example(zle -C _next_tags complete-word _next_tags
+bindkey '^Xn' _next_tags)
 )
 findex(_read_comp (^X^R))
 item(tt(_read_comp (^X^R)))(

--
Sven Wischnowsky                         wischnow@informatik.hu-berlin.de


             reply	other threads:[~2000-03-20 10:54 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-03-20 10:54 Sven Wischnowsky [this message]
  -- strict thread matches above, loose matches on Subject: below --
2000-03-20 10:40 Sven Wischnowsky
2000-03-20  9:56 Sven Wischnowsky
2000-03-20 10:22 ` 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=200003201054.LAA10458@beta.informatik.hu-berlin.de \
    --to=wischnow@informatik.hu-berlin.de \
    --cc=zsh-workers@sunsite.auc.dk \
    /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).