From: "Bart Schaefer" <schaefer@candle.brasslantern.com>
To: Zsh workers <zsh-workers@sunsite.dk>
Subject: Re: Moving completion functions
Date: Thu, 22 Mar 2001 16:29:18 -0800 [thread overview]
Message-ID: <010322162918.ZM21205@candle.brasslantern.com> (raw)
In-Reply-To: <3ABA72A9.EB9C68FC@u.genie.co.uk>
On Mar 22, 9:46pm, Oliver Kiddle wrote:
> Subject: Re: Moving completion functions
>
> > Functions/Misc/acx Functions/Examples # Misc?
> > Functions/Misc/cx Functions/Examples # Misc?
>
> I'd delete these because they would be better written as aliases.
I agree, which (jumping ahead) is why I do NOT agree with:
> I would class acx, cx, harden, proto, yp, yu, checkmail, mere, zed
> and zmv as useful functions which many people might want to use.
I would include harden, checkmail, mere, and definitely zed as "useful
functions which many people might want to use," but proto is marginal
(how many people code in C with exactly Paul Falstad's style?) and to
autoload all those those trivial one-liners is IMO a waste.
> > Functions/Misc/multicomp Functions/Compctl
>
> Is this one still relevant now that we have matching control.
It's too big to reasonably put in compctl-examples and remains relevant
to anyone not using the new completion system. (multicomp is like the
_path_files function; no real overlap with matching control AFAICT.)
> > Functions/Misc/promptnl Functions/Misc
>
> This is new right? Was this something to do with evading the promptcr
> problem?
Yes, you call promptnl from precmd. I suppose it (or contrib.yo) should
say that, somewhere.
> > Functions/Misc/run-help Functions/Misc # Add #autoload line?
>
> On the basis that functions starting #autoload are autoloaded by
> compinit, and that #autoload was intended for functions which are part
> of the completion system, should we be using #autoload in
> non-completion system related functions.
That's why there's a `?' at the end of my comment. So, leave run-help
as it is.
> > Functions/Misc/zless Functions/Misc
>
> I'd delete this one too because of the LESSPIPE feature in recent
> versions of less. It could always be found a good home on the web
> pages. If it stays, I'd put it in Examples.
I have no objection to moving this to Example.
> > Functions/Misc/zls Functions/Misc
>
> This I'd definitely put in Examples. I can't believe anyone would use
> it instead of their binary ls but it is a nice example for the stat
> module.
This is also fine with me.
> I agree with the Compctl division although it might be better to put
> them in the compctl-examples file to get them out of the way.
I'd actually rather split compctl-examples up into smaller files and put
them all in Functions/Compctl, but I suppose we're trying to discourage
use of compctl ...
> The example startup files are another thing we should look at before
> 4.0. I'd be in favour of modifying them to use new-style completion and
> having some typical example zstyles and generally to be a bit more
> up-to-date. If there is agreement on this, I'll come up with a
> suggested patch for them.
The main thing I want to do with the example startup files is to add a
batch of comments, possibly in all-caps, telling system administrators
NOT to drop these files into /etc/z*. And maybe even put a "return 0"
at the top of each file just in case some nimrod copies them to /etc/
without looking at them.
next prev parent reply other threads:[~2001-03-23 0:30 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-22 21:46 Oliver Kiddle
2001-03-22 21:50 ` Oliver Kiddle
2001-03-23 0:29 ` Bart Schaefer [this message]
2001-03-25 15:26 ` Oliver Kiddle
2001-03-25 20:39 ` Peter Stephenson
2001-03-25 23:27 ` PATCH: nimrod proofing Bart Schaefer
2001-03-25 23:35 ` Bart Schaefer
2001-03-26 4:33 ` Moving completion functions 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-29 9:33 Sven Wischnowsky
2001-03-29 16:49 ` 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 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=010322162918.ZM21205@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).