From: Oliver Kiddle <opk@u.genie.co.uk>
To: zsh-workers@sunsite.dk
Subject: PATCH: Re: A few problems with 4.0.1-pre-1
Date: Wed, 28 Feb 2001 16:27:44 +0000 [thread overview]
Message-ID: <20010228162744.A18755@rambo.logica.co.uk> (raw)
Paul Ackersviller wrote:
> I just installed zsh 4.0.1-pre-1 from CVS and was getting errors from
> _main_complete. This used to work for me a couple of months ago, so I
Thanks for the bug report. The problem is exactly as you described. The
trouble is that when ksh_arrays is set, $_comp_options only expands to the
first element of the _comp_options array - in the same way the ksh
does. This patch should fix it by using ${_comp_options[@]} instead to
expand to all elements in _comp_options.
I'm not sure about your second problem but I'll have a closer look.
The third problem is not really a problem. You don't have Yodl installed
so the documentation can't be generated. Normally these would be prebuilt
but they aren't if you download from CVS or one of the dev versions. Maybe
we should do something different here if the configure script doesn't find
Yodl because it doesn't look good. Any ideas?
Oliver Kiddle
Index: Completion/Core/_main_complete
===================================================================
RCS file: /cvsroot/zsh/zsh/Completion/Core/_main_complete,v
retrieving revision 1.43
diff -u -u -r1.43 _main_complete
--- Completion/Core/_main_complete 2000/10/19 08:58:17 1.43
+++ Completion/Core/_main_complete 2001/02/28 16:19:08
@@ -16,7 +16,7 @@
# which makes the output of setopt and unsetopt reflect a different
# state than the global one for which you are completing.
-setopt localoptions $_comp_options
+setopt localoptions ${_comp_options[@]}
exec </dev/null # ZLE closes stdin, which can cause errors
reply other threads:[~2001-02-28 16:27 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20010228162744.A18755@rambo.logica.co.uk \
--to=opk@u.genie.co.uk \
--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).