zsh-workers
 help / color / mirror / code / Atom feed
From: Bruce Stephens <B.Stephens@isode.com>
To: zsh-workers@sunsite.auc.dk
Subject: Out of the box user experience
Date: 16 Mar 1999 13:31:50 +0000	[thread overview]
Message-ID: <vbpv694l2x.fsf@snake.isode.com> (raw)

I'm a bit unhappy about all these completion scripts not being
installed somewhere.  How about sticking them in $prefix/lib/zsh/ (in
suitable subdirectories---maybe version-specific?), and adding a
shell-set parameter, ZSH_SCRIPTS or ZSH_LIB or something, so it's easy
to find them.

Then the suggestions in the README can be made more concrete for new
users (we could even provide a script to do it).  Something like:

        % zsh -f
        % mkdir ~/completion
        % cp $ZSH_LIB/**/*(.) ~/completion
        % touch ~/.zshrc; echo 'fpath=(~/completion $fpath)' >> .zshrc
        % echo '[[ -f ~/completion/compinit ]] && . ~/completion/compinit -d' >> .zshrc

or something.  I like the idea of individual users being able to have
whatever completions they like, and to be able to avoid ones that they
don't want, but I'd like it to be as easy as possible.  (Perhaps we'd
want just "cp $ZSH_LIB/{Core,Base,User}/* ~/completion", or something,
assuming that there'd be lots of seriously optional scripts.)

Hmm.  There are other scripts that could be installed, too, which
aren't completion-related.  Maybe it has to be
$ZSH_LIB/Completion/{Core,...


On a different topic, I noticed some typos in the new documentation.
Would it be helpful if I took the pws-12 docs and checked them?  I
don't guarantee to spot errors (since there's lots of stuff I just
don't understand), but I'm likely to spot most spelling errors and the
more obvious things.  Or would it be better if I waited for a bit
longer (when things are closer to a release)?


             reply	other threads:[~1999-03-16 13:33 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-03-16 13:31 Bruce Stephens [this message]
1999-03-16 13:37 ` Peter Stephenson
1999-03-16 14:24   ` Bruce Stephens
1999-03-16 16:08     ` Bart Schaefer
1999-03-16 16:26       ` Bruce Stephens

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=vbpv694l2x.fsf@snake.isode.com \
    --to=b.stephens@isode.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).