From: "Bart Schaefer" <schaefer@candle.brasslantern.com>
To: zsh-workers@sunsite.dk
Subject: Re: Moving completion functions
Date: Wed, 28 Mar 2001 16:14:01 +0000 [thread overview]
Message-ID: <1010328161401.ZM16238@candle.brasslantern.com> (raw)
In-Reply-To: <200103281412.QAA07394@beta.informatik.hu-berlin.de>
On Mar 28, 4:12pm, Sven Wischnowsky wrote:
}
} I really only have a suggestion for _compalso: putting it into
} Base/Utility and renaming it to `_contexts' because it completes
} everything for the context described in the arguments, just like
} _arguments and other functions in Utility.
That sounds like a fine idea to me.
} And a better name for `_wanted' might be `_offer', but that doesn't
} make it easier to find in a directory listing, of course. Although it
} would end up just before `_requested' and there are only twelve
} functions in the directory anyway.
That one is a toss-up. I don't know whether _offer is better than _wanted.
The number of functions in the directory isn't an issue.
} Twelve, unless we move the _call_* function into the Utility directory,
} too, which seems sensible, somehow.
Yes, that does seem sensible.
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.
--
Bart Schaefer Brass Lantern Enterprises
http://www.well.com/user/barts http://www.brasslantern.com
Zsh: http://www.zsh.org | PHPerl Project: http://phperl.sourceforge.net
next prev parent reply other threads:[~2001-03-28 16:14 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-28 14:12 Sven Wischnowsky
2001-03-28 16:14 ` Bart Schaefer [this message]
2001-03-28 16:20 ` Peter Stephenson
-- 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-29 9:33 Sven Wischnowsky
2001-03-29 16:49 ` Bart Schaefer
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=1010328161401.ZM16238@candle.brasslantern.com \
--to=schaefer@candle.brasslantern.com \
--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).