zsh-workers
 help / color / mirror / code / Atom feed
From: "Bart Schaefer" <schaefer@candle.brasslantern.com>
To: Alexandre Duret-Lutz <alexandre.duret@greyc.ismra.fr>,
	zsh-workers@sunsite.auc.dk
Subject: Re: PATCH: _argument, a repeated local, again
Date: Mon, 22 Nov 1999 18:04:58 +0000	[thread overview]
Message-ID: <991122180458.ZM22609@candle.brasslantern.com> (raw)
In-Reply-To: <7dpux2wgpg.fsf@venus.l2i>

On Nov 22,  5:59pm, Alexandre Duret-Lutz wrote:
} Subject: PATCH: _argument, a repeated local, again
}
} That was a local left in a while loop.

I'm not sure which version of _arguments you were diffing against; the
line "nm -eq compstate[nmatches] ]]; then" was replaced at least as far
back as zsh-workers/8603, and isn't present in -pws-9.  Here's the diff
against -pws-9 plus zsh-workers/8722.

Index: Completion/Base/_arguments
===================================================================
@@ -166,7 +166,7 @@
 if comparguments -i "$autod" "$@"; then
   local nm="$compstate[nmatches]" action noargs aret expl local
   local next direct odirect equal single match matched ws tmp1 tmp2
-  local opts subc
+  local opts subc prefix suffix
 
   if comparguments -D descr action; then
     comparguments -C subc
@@ -289,8 +289,6 @@
       if [[ -n "$opts" && -z "$aret$matched" &&
             nm -ne compstate[nmatches] ]] &&
           _requested arguments; then
-
-        local prefix suffix
 
         prefix="${PREFIX#*\=}"
         suffix="$SUFFIX"

-- 
Bart Schaefer                                 Brass Lantern Enterprises
http://www.well.com/user/barts              http://www.brasslantern.com


  reply	other threads:[~1999-11-22 18:05 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-11-22 17:59 Alexandre Duret-Lutz
1999-11-22 18:04 ` Bart Schaefer [this message]
1999-11-22 19:35 ` Alexandre Duret-Lutz
1999-11-22 19:24   ` Bart Schaefer
1999-11-22 19:34     ` 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=991122180458.ZM22609@candle.brasslantern.com \
    --to=schaefer@candle.brasslantern.com \
    --cc=alexandre.duret@greyc.ismra.fr \
    --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).