From: John Beppu <beppu@ax9.org>
To: zsh-workers <zsh-workers@sunsite.auc.dk>
Subject: Re: completion differences between shells writeup
Date: Wed, 20 Feb 2002 15:14:37 -0800 [thread overview]
Message-ID: <20020220151437.A14484@Ax9.org> (raw)
In-Reply-To: <20020219065214.53796.qmail@web10406.mail.yahoo.com>
[ date ] 2002/02/18 | Monday | 10:52 PM
[ author ] Felix Rosencrantz <f_rosencrantz@yahoo.com>
> Considering
> all the functionality that zsh has now, it might be useful to have a shell
> completion comparison list. It could easily cover a large number of features
> (fakes, arguments, descriptions, debugging, customization, pre-written
> functions, matching control, tags, ....)
<tangent>
I wrote a piece titled "Making the Transition to # scheduled for the
Zsh" for my column in Linux Magazine, and it's a # May 2002 issue
real light introduction to zsh written w/ bash
users in mind. The first thing I tell them is to
do is put:
autoload -U compinit
compinit
in their .zshrc, and then I go on to give examples
of some of the completions that come standard with
zsh. (That's usually enough make people really
curious.) Aside from completions, I also
introduce setopt and some of the prepackaged
prompts. I figured that w/ a basic understanding
of those 3 topics, people would be able to quickly
get up to speed.
After I wrote it, I sent it out to some of my friends,
and I got most of them to switch, and those who
didn't switch right away expressed strong interest
in switching in the near future. ...so zsh does
a good job of standing on its own merits -- it's
just a matter of educating people about what zsh
is capable of AND (most importantly) that it's
surprisingly easy to get a powerful configuration
going. If people knew this, there'd be a lot more
zsh users out there.
I think it's just a matter of writing a short
guide to porting your bash configuration to zsh
and then harnessing the Slashdot Effect. ;-)
</tangent>
Would you believe I've been using zsh for less than a
month? I love it, though, and I plan on writing a few
more pieces on zsh, too. I'd really like to learn how
to create my own program-specific completions, but
before I do that, I think I'd probably have to provide
a short overview of some of zsh's scripting abilities
(that aren't found in /bin/sh).
Any references would be greatly appreciated.
PS: I'd like to try zftp out, but I have no idea how
enable it. Yes, I've RTFM'd, and I've concluded
that I didn't compile the zftp module when I built
zsh, but when I run ./configure --help, there's no
--enable-zftp option, so I'm kinda lost... help.
--
package wuv'apqvjgt;($_=join('',(*PgtnHcemgt))) # print map "beppu\@$_\n", qw(
=~ s/([HaP])(?!e)/ \U>$1/g;s/^.|:| (?=A)|>//g;y # cpan.org lbox.org binq.org
/c-z/a-u/;print"J$_\n";#$^%$^X@.^ <!-- japh --> # oss.lineo.com codepoet.org);
next prev parent reply other threads:[~2002-02-20 23:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-19 6:52 Felix Rosencrantz
2002-02-20 23:14 ` John Beppu [this message]
2002-02-21 4:19 ` Bart Schaefer
2002-02-21 20:53 ` John Beppu
2002-02-22 9:31 ` Oliver Kiddle
2002-02-22 18:13 ` John Beppu
2002-02-21 13:12 ` 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=20020220151437.A14484@Ax9.org \
--to=beppu@ax9.org \
--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).