From: "Bart Schaefer" <schaefer@brasslantern.com>
To: zsh-workers@sunsite.auc.dk
Subject: Re: PATCH: matching in the new completion system
Date: Tue, 27 Apr 1999 21:37:59 -0700 [thread overview]
Message-ID: <990427213759.ZM29782@candle.brasslantern.com> (raw)
In-Reply-To: <199904261339.PAA08495@beta.informatik.hu-berlin.de>
On Apr 26, 3:39pm, Sven Wischnowsky wrote:
} Subject: Re: PATCH: matching in the new completion system
}
} All this is a bit like saying `hey, compadd, this is the list of
} strings I'm working on (the array) and here are the parts of the
} strings you should try to match (the words), modify the list for me'.
I thought I was following this, until I got to (the words). Could you
please give an example?
} So, what do you think? Is this worth including? Should we continue to
} search for a better way? Any suggestions?
A mostly-unrelated one: Now that you have the addmatches() parameters
broken out into a struct, could you attach a comment to each line to
explain what the field represents?
--
Bart Schaefer Brass Lantern Enterprises
http://www.well.com/user/barts http://www.brasslantern.com
next prev parent reply other threads:[~1999-04-28 4:38 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-04-26 13:39 Sven Wischnowsky
1999-04-26 13:25 ` Peter Stephenson
1999-04-28 4:37 ` Bart Schaefer [this message]
-- strict thread matches above, loose matches on Subject: below --
1999-04-28 7:44 Sven Wischnowsky
1999-04-14 8:31 Sven Wischnowsky
1999-04-14 6:19 Sven Wischnowsky
1999-04-14 7:50 ` Peter Stephenson
1999-04-13 13:18 Sven Wischnowsky
1999-04-13 14:39 ` Peter Stephenson
1999-04-14 6:15 ` Andrej Borsenkow
1999-04-13 10:39 Sven Wischnowsky
1999-04-12 9:07 Sven Wischnowsky
1999-04-13 9:56 ` Andrej Borsenkow
1999-04-13 12:46 ` Andrej Borsenkow
1999-04-13 12:35 ` 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=990427213759.ZM29782@candle.brasslantern.com \
--to=schaefer@brasslantern.com \
--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).