From: Adam Spiers <adam@thelonious.new.ox.ac.uk>
To: zsh-workers@sunsite.auc.dk
Subject: Re: simulation of dabbrev-expand
Date: Mon, 20 Sep 1999 23:00:59 +0100 [thread overview]
Message-ID: <19990920230059.A12352@thelonious.new.ox.ac.uk> (raw)
In-Reply-To: <199909200840.KAA06286@beta.informatik.hu-berlin.de>
Sven Wischnowsky (wischnow@informatik.hu-berlin.de) wrote:
>
> Adam Spiers wrote:
>
> > How can I ensure that there are no duplicate words in the list of
> > matches? Even if this isn't the real problem I'm experiencing, it may
> > well help narrow it down.
>
> Bart Schaefer answered:
>
> > The completion system *should* be handling this for you, but I'm going to
> > leave that bug to Sven, [ ... ]
>
> Hm, actually I don't think this is a bug -- at least it is intended
> behaviour. Although I admit that I partly did this for performance
> reasons. So, should duplicates always be removed or should this be an
> option (we're in trouble with `compctl', then -- no more option
> letters).
I'd vote for the option er, option ... sorry :-) No idea what you
should do about the option letters, other than using 8-bit-high
options ;-)
> You've missed some mails in which I wrote something about this. See
> 6117 and 6119 (and somewhere before that, but I don't have this in my
> list any more, it seems).
Thanks; interesting reading.
next prev parent reply other threads:[~1999-09-20 22:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-09-20 8:40 Sven Wischnowsky
1999-09-20 22:00 ` Adam Spiers [this message]
-- strict thread matches above, loose matches on Subject: below --
1999-09-22 14:11 Sven Wischnowsky
1999-09-22 14:57 ` Zefram
1999-09-22 22:13 ` Adam Spiers
1999-09-21 7:28 Sven Wischnowsky
1999-09-21 7:20 Sven Wischnowsky
1999-09-22 0:03 ` Adam Spiers
[not found] <19990909133913.A30055@thelonious.new.ox.ac.uk>
[not found] ` <990909171104.ZM15814@candle.brasslantern.com>
[not found] ` <19990916173409.A17932@thelonious.new.ox.ac.uk>
1999-09-17 21:44 ` Adam Spiers
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=19990920230059.A12352@thelonious.new.ox.ac.uk \
--to=adam@thelonious.new.ox.ac.uk \
--cc=adam@spiers.net \
--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).