From: Bart Schaefer <schaefer@brasslantern.com>
To: zsh-workers@sunsite.dk
Subject: Re: Bug#236350: zsh: _prefix completer broken?
Date: Sat, 6 Mar 2004 17:59:20 +0000 [thread overview]
Message-ID: <1040306175920.ZM6151@candle.brasslantern.com> (raw)
In-Reply-To: <1040306173839.ZM5329@candle.brasslantern.com>
On Mar 6, 5:38pm, Bart Schaefer wrote:
} Subject: Re: Bug#236350: zsh: _prefix completer broken?
}
} schaefer<504> egrefoo
} No matches for `external command', `builtin command', `shell function',
} `alias', `suffix alias', `reserved word', `job', `parameter', `local
} directory', `directory in cdpath', or `corrections'
}
} : _main_complete:159:for for elif-then; ret=0
} : _main_complete:160:for for elif-then; break 2 <-- doesn't happen in 4.0.7
} : _main_complete:169; curcontext=:::
} : _main_complete:170; nm=0
This looks like it could be a serious problem. The code in question is
this:
if [[ -n "$call" ]]; then
if "${(@)argv[3,-1]}"; then
ret=0
break 2
fi
elif "$tmp"; then
ret=0
break 2
fi
_approximate is being called as "$tmp" here. It returns 1, but the
test succeeds and breaks out of the loop, because _approximate uses
"trap 'unfunction compadd' EXIT INT" and the return code of the trap
is being propagated rather than the return code of _approximate.
next prev parent reply other threads:[~2004-03-06 17:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1AzKUu-0003tz-00@techloaner2.idiomtech.com>
2004-03-06 1:35 ` Clint Adams
2004-03-06 16:05 ` Andrew Pimlott
2004-03-06 17:38 ` Bart Schaefer
2004-03-06 17:59 ` Bart Schaefer [this message]
2004-03-06 18:03 ` Oliver Kiddle
2004-03-06 23:32 ` Bart Schaefer
2004-03-08 10:41 ` Peter Stephenson
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=1040306175920.ZM6151@candle.brasslantern.com \
--to=schaefer@brasslantern.com \
--cc=zsh-workers@sunsite.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).