From: Zefram <zefram@fysh.org>
To: wischnow@informatik.hu-berlin.de (Sven Wischnowsky)
Cc: zsh-workers@sunsite.auc.dk
Subject: Re: simulation of dabbrev-expand
Date: Wed, 22 Sep 1999 15:57:29 +0100 (BST) [thread overview]
Message-ID: <E11Tnpp-00014q-00@crucigera.fysh.org> (raw)
In-Reply-To: <199909221411.QAA20959@beta.informatik.hu-berlin.de> from Sven Wischnowsky at "Sep 22, 1999 4:11:37 pm"
Sven Wischnowsky wrote:
>Ok. This makes `-1' keep the completion system from removing all
>duplicates and `-2' keep it from removing consecutive duplicates. Yes,
>the sense is reversed so that `-J' still gives the normal behaviour.
So you mean
neither option = remove all duplicates
-1 = keep non-consecutive duplicates and remove consecutive duplicates
-2 = keep all duplicates
>In other words:
>-V -- unsorted list without duplicates
>-V1 -- unsorted list with only non-consecutive duplicates
>-V2 -- unsorted list with all duplicates
OK
>-J -- sorted list without duplicates
>-J1 -- sorted list with duplicates (which are all consecutive due to
> the sorting)
>-J2 -- same as -J1
That can't be right. -J1 should be removing consecutive duplicates,
i.e., all duplicates due to the sorting. Shouldn't it?
>+item(tt(-2))(
>+If given together with the tt(-J) option, behaves the same as
>+tt(-J).
This looks fishy too.
-zefram
next prev parent reply other threads:[~1999-09-22 14:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-09-22 14:11 Sven Wischnowsky
1999-09-22 14:57 ` Zefram [this message]
1999-09-22 22:13 ` Adam Spiers
-- strict thread matches above, loose matches on Subject: below --
1999-09-21 7:28 Sven Wischnowsky
1999-09-21 7:20 Sven Wischnowsky
1999-09-22 0:03 ` Adam Spiers
1999-09-20 8:40 Sven Wischnowsky
1999-09-20 22:00 ` 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=E11Tnpp-00014q-00@crucigera.fysh.org \
--to=zefram@fysh.org \
--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).