From: Sven Wischnowsky <wischnow@informatik.hu-berlin.de>
To: zsh-workers@sunsite.dk
Subject: Re: PATCH: MH for Mailboxes (TM)
Date: Thu, 29 Mar 2001 10:36:50 +0200 (MET DST) [thread overview]
Message-ID: <200103290836.KAA20226@beta.informatik.hu-berlin.de> (raw)
In-Reply-To: "Bart Schaefer"'s message of Wed, 28 Mar 2001 15:53:43 +0000
Bart Schaefer wrote:
> On Mar 28, 12:55pm, Sven Wischnowsky wrote:
> } Subject: Re: PATCH: MH for Mailboxes (TM)
> }
> } > However, at _multi_parts line 164-166, the expression
> } >
> } > "${(@)${(@M)matches:#*${sep}}%%${sep}*}"
> } >
> } > expands to the empty string. Could that be the source of the problem?
> }
> } Yes, that may be. Even if it doesn't fix this particular problem, the
> } patch below should only make things saver.
> }
> } Can someone try?
>
> I still get the blank item in the list after your patch. I think maybe
> the problem is that tmp1 gets an empty element at line 94, which then
> gets added as a match at line 120, but I tried duplicating your change
> at line 94 without any better result.
Hm. After setting up some parameters I was able to reproduce it. But
for me changing lines 94 and 97 fixed it. So I'll commit the patch
below anyway.
> Does `compadd -a array' where the array is empty have a bad effect?
No, that works nicely (having tried it with a simple test completion
function).
That _mailboxes function... there are some wrongly indented parts in
it. And the `pinedirectory', `maildirectory' and `mailpath'
parameters don't seem to be documented. Are these standard names?
(In particular, mailpath even isn't a local.)
Bye
Sven
Index: Completion/Core/_multi_parts
===================================================================
RCS file: /cvsroot/zsh/zsh/Completion/Core/_multi_parts,v
retrieving revision 1.6
diff -u -r1.6 _multi_parts
--- Completion/Core/_multi_parts 2001/03/28 10:58:02 1.6
+++ Completion/Core/_multi_parts 2001/03/29 08:31:28
@@ -91,10 +91,10 @@
else
# No exact match, see how many strings match what's on the line.
- builtin compadd -O tmp1 - "${(@)matches%%${sep}*}"
+ builtin compadd -O tmp1 - "${(@)${(@)matches%%${sep}*}:#}"
[[ $#tmp1 -eq 0 && -n "$_comp_correct" ]] &&
- compadd -O tmp1 - "${(@)matches%%${sep}*}"
+ compadd -O tmp1 - "${(@)${(@)matches%%${sep}*}:#}"
if [[ $#tmp1 -eq 1 ]]; then
--
Sven Wischnowsky wischnow@informatik.hu-berlin.de
next reply other threads:[~2001-03-29 8:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-29 8:36 Sven Wischnowsky [this message]
2001-03-29 8:52 ` Bart Schaefer
-- strict thread matches above, loose matches on Subject: below --
2001-03-28 10:55 Sven Wischnowsky
2001-03-28 15:53 ` Bart Schaefer
2001-03-26 8:34 Sven Wischnowsky
2001-03-28 6:30 ` Bart Schaefer
2001-03-23 17:22 Peter Stephenson
2001-03-24 18:06 ` Bart Schaefer
2001-03-24 23:55 ` 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=200103290836.KAA20226@beta.informatik.hu-berlin.de \
--to=wischnow@informatik.hu-berlin.de \
--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).