From: "Bart Schaefer" <schaefer@candle.brasslantern.com>
To: Sven Wischnowsky <wischnow@informatik.hu-berlin.de>,
zsh-workers@sunsite.auc.dk
Subject: Re: Something else wrong with _multi_parts
Date: Mon, 21 Feb 2000 10:42:14 +0000 [thread overview]
Message-ID: <1000221104214.ZM16658@candle.brasslantern.com> (raw)
In-Reply-To: <200002211001.LAA05566@beta.informatik.hu-berlin.de>
On Feb 21, 11:01am, Sven Wischnowsky wrote:
} Subject: Re: Something else wrong with _multi_parts
}
} Bart Schaefer wrote:
}
} > names=( foo bar home/test /usr/tmp /tmp/foo )
} > _multi_parts / names
} >
} > Only (/usr/tmp /tmp/foo) make it into the `matches' array in _multi_parts.
}
} At one point while building this patch I got (with /<TAB>) the matches
} `/' and `home'. Somehow, this is correct, but I think the behaviour
} this shows now is more intuitive.
Hmm, using the _mailboxes that I just sent, I get offered two matches at
this point:
zagzig[152] mail -f /usr<TAB>
/usr/
usr/
That certainly can't be right. Looking at a fragment of an xtrace:
[...]
+_multi_parts:84> tmp1=( usr/mail/schaefer usr/spool/mail/schaefer )
+_multi_parts:89> (( 2 ))
+_multi_parts:90> npref=usr/
+_multi_parts:216> matches=( mail/schaefer spool/mail/schaefer )
+_multi_parts:217> pref=/usr/
+_multi_parts:221> [[ usr == */* ]]
+_multi_parts:224> [[ == */* ]]
+_multi_parts:233> PREFIX=/usr
+_multi_parts:234> SUFFIX=
+_multi_parts:236> [[ -n /usr/ && /usr != /usr/ ]]
+_multi_parts:237> compadd -J -default- -S -M r:|/=* r:|=* - /usr/
+_multi_parts:240> return
[...]
+_path_files:517> compadd -Qf -J all-files -F _comp_ignore -p / -W / -M r:|/=* r:|=* - usr
It appears that _multi_parts is compadding "/usr/" and _path_files is
compadding "usr". I expected them both to "compadd ... usr".
--
Bart Schaefer Brass Lantern Enterprises
http://www.well.com/user/barts http://www.brasslantern.com
next prev parent reply other threads:[~2000-02-21 10:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-02-21 10:01 Sven Wischnowsky
2000-02-21 10:42 ` Bart Schaefer [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-02-21 9:41 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=1000221104214.ZM16658@candle.brasslantern.com \
--to=schaefer@candle.brasslantern.com \
--cc=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).