From: Sven Wischnowsky <wischnow@informatik.hu-berlin.de>
To: zsh-workers@sunsite.dk
Subject: Re: Moving completion functions
Date: Thu, 29 Mar 2001 11:33:15 +0200 (MET DST) [thread overview]
Message-ID: <200103290933.LAA20464@beta.informatik.hu-berlin.de> (raw)
In-Reply-To: "Bart Schaefer"'s message of Wed, 28 Mar 2001 16:14:01 +0000
Bart Schaefer wrote:
> ...
>
> BTW, a remark on my sectioning scheme for the Test directory: Section Y
> is for tests of builtin interactive commands/constructs (select, read -q,
> etc.) where the tests themselves need to use the zpty module, which will
> (eventually) have been tested in section X ...
>
> We might want to add description of this naming to a Test/README or to the
> comments in ztst.zsh.
Hmhm.
Felix Rosencrantz wrote:
> ...
>
> I've been busy and away, so I'm quite a bit behind on the mailing list. But
> just wanted to stick my nose in.... It might be worth splitting completion and
> the rest of zle in to separate sections. Both of these modules represent
> a lot of space in the documentation and code. Because there is a lot of
> code/functionality that can be tested, it seems like it would be worthwhile to
> give each a separate section.
That sounds sensible. Maybe start using lower-case letters for the
parts that are big enough to be called `systems', i.e. completion and
zftp and later probably more?
Peter Stephenson wrote:
> ... [ _wanted and firends ]
>
> In that case, better leave it, in case anyone's being looking at the user
> guide, which makes quite heavy use of _wanted.
That's fine with me.
and Bart again:
> I won't commit these yet (hence they're not presented in diff form); either
> Sven can add them at the Great Renaming, or I'll add them after it happens.
I've added that to the todo-list in the script.
> The only reason for using _arguments in fned is to get "no more arguments"
> behavior after the first name is completed; otherwise it could simply
> call _functions directly.
Or test [[ CURRENT -gt 2 ]] directly...
Bye
Sven
--
Sven Wischnowsky wischnow@informatik.hu-berlin.de
next reply other threads:[~2001-03-29 9:33 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-29 9:33 Sven Wischnowsky [this message]
2001-03-29 16:49 ` Bart Schaefer
-- strict thread matches above, loose matches on Subject: below --
2001-03-30 14:00 Sven Wischnowsky
2001-03-30 15:12 ` Bart Schaefer
2001-03-28 14:12 Sven Wischnowsky
2001-03-28 16:14 ` Bart Schaefer
2001-03-28 16:20 ` Peter Stephenson
2001-03-26 14:16 Sven Wischnowsky
2001-03-26 8:53 Sven Wischnowsky
2001-03-22 21:46 Oliver Kiddle
2001-03-22 21:50 ` Oliver Kiddle
2001-03-23 0:29 ` Bart Schaefer
2001-03-25 15:26 ` Oliver Kiddle
2001-03-25 20:39 ` Peter Stephenson
2001-03-26 4:33 ` Bart Schaefer
2001-03-22 10:40 Sven Wischnowsky
2001-03-22 11:03 ` Peter Stephenson
2001-03-22 17:04 ` Bart Schaefer
2001-03-21 11:42 Sven Wischnowsky
2001-03-20 21:32 Oliver Kiddle
2001-03-21 9:58 ` Bart Schaefer
2001-03-19 9:46 Sven Wischnowsky
2001-03-22 7:21 ` Bart Schaefer
2001-03-18 22:20 Oliver Kiddle
2001-03-19 4:36 ` Bart Schaefer
2001-03-16 17:27 Oliver Kiddle
2001-03-16 10:20 Sven Wischnowsky
2001-03-18 2:39 ` Bart Schaefer
2001-03-15 20:50 Oliver Kiddle
2001-03-16 12:09 ` Peter Stephenson
2001-03-17 23:16 ` Bart Schaefer
2001-03-15 15:46 Oliver Kiddle
2001-03-15 18:14 ` Bart Schaefer
2001-03-15 10:43 Sven Wischnowsky
2001-03-15 9:30 Sven Wischnowsky
2001-03-15 10:33 ` Peter Stephenson
2001-03-15 17:04 ` 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=200103290933.LAA20464@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).