zsh-users
 help / color / mirror / code / Atom feed
From: Bruce Stephens <b.stephens@isode.com>
To: zsh-users@sunsite.auc.dk
Subject: Re: o'reilly zsh book?
Date: 25 Jan 1999 17:06:18 +0000	[thread overview]
Message-ID: <vbg18zth85.fsf@snake.isode.com> (raw)

Sweth Chandramouli <sweth@astaroth.nit.gwu.edu> writes:

> as always, i find myself amazed at what zsh can do, and totally
> frustrated at the documentation.

I'd like to see more tutorial-style documentation.  Not just reference
material, but something showing me how to use zsh for things I'm
likely to want to do.  

(Aside: one thing that really annoys me is computing magazines
comparing Unix command lines to DOS.  The DOS command line is crud,
but that doesn't imply that all command lines are crud.  But if you
come to bash or zsh from DOS, then probably you wouldn't see anything
other than an irritatingly case-sensitive DOS, simply because you
wouldn't know what to do with all the extra stuff.)

> i've been thinking for a while that what zsh really needs is one of
> those o'reilly handbooks to be written about it, and more recently,
> i've come to the conclusion that that probably isn't going to happen
> anytime soon.

There's a potential problem of market: does anyone have any idea how
many people use zsh?  I'd buy an O'Reilly book on it.

> and would the list as a whole be opposed to being a sounding board
> for any questions that might come up?

I don't see a problem in that.

Alternatively, you could help to improve the documentation that comes
with zsh.  That would have the disadvantages that you wouldn't get any
money from it, and there wouldn't be a nice printed version (which
would be nice).  But even if O'Reilly (or whoever) turned down your
proposal, you could still contribute to the free documentation.

"Linux Programming Tools" has a chapter on zsh, but it's horribly
limited.  It doesn't even mention things like $(...), which also exist
in bash.  It's not a bad book, but I certainly wouldn't recommend it
as anything other than an imperfect reference book.  The Tcl/Tk tables
use an invalid syntax, too.


             reply	other threads:[~1999-01-25 17:06 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-01-25 17:06 Bruce Stephens [this message]
  -- strict thread matches above, loose matches on Subject: below --
1999-01-27  9:26 Karsten Thygesen
1999-01-26 12:53 Bruce Stephens
1999-01-26 12:48 Duncan Sinclair
1999-01-26 10:44 Chavdar Ivanov
1999-01-26 10:40 Thomas Koehler
1999-01-26 10:33 Bruce Stephens
1999-01-26 10:26 Bruce Stephens
1999-01-26  9:27 Timothy Writer
1999-01-26  9:07 Peter Stephenson
1999-01-26  1:36 Oliver Kiddle
1999-01-25 18:11 Sweth Chandramouli
1999-01-25 17:59 Matt Armstrong
1999-01-25 17:58 Bruce Stephens
1999-01-25 17:52 Sweth Chandramouli
1999-01-25 17:32 Bart Schaefer
1999-01-25 16:48 Sweth Chandramouli

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