zsh-workers
 help / color / mirror / code / Atom feed
From: Sven Wischnowsky <wischnow@informatik.hu-berlin.de>
To: zsh-workers@sunsite.auc.dk
Subject: PATCH: parameters in command position
Date: Thu, 6 Jan 2000 13:52:00 +0100 (MET)	[thread overview]
Message-ID: <200001061252.NAA17972@beta.informatik.hu-berlin.de> (raw)


I forgot... now that user's can say that they don't want to see
certain types of matches we probably should complete parameters in
command position, too. Maybe the auto-suffix should be `=(' for arrays 
and hashes.

This also removes the comment from _parameter because looking at
_parameters will tell you nothing about -e any more.

Bye
 Sven

diff -ru ../z.old/Completion/Base/_command_names Completion/Base/_command_names
--- ../z.old/Completion/Base/_command_names	Thu Jan  6 13:27:35 2000
+++ Completion/Base/_command_names	Thu Jan  6 13:42:55 2000
@@ -22,6 +22,7 @@
     'aliases:alias:compadd - ${(@k)aliases}'
     'reserved-words:reserved word:compadd - ${(@k)reswords}'
     'jobs:: _jobs -t'
+    'parameters:: _parameters -qS= -r "\n\t\- =["'
   )
 fi
 
diff -ru ../z.old/Completion/Base/_parameter Completion/Base/_parameter
--- ../z.old/Completion/Base/_parameter	Thu Jan  6 13:27:35 2000
+++ Completion/Base/_parameter	Thu Jan  6 13:48:11 2000
@@ -1,12 +1,3 @@
 #compdef -parameter-
 
 _tags parameters && _parameters -e
-
-# Without the `-e' option, we would use the following (see the file
-# Core/_parameters for more enlightenment).
-
-# if [[ "$compstate[insert]" = *menu* ]]; then
-#   _parameters -s ''
-# else
-#   _parameters -s ' '
-# fi

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


             reply	other threads:[~2000-01-06 12:52 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-01-06 12:52 Sven Wischnowsky [this message]
2000-01-06 14:40 Sven Wischnowsky

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=200001061252.NAA17972@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).