zsh-workers
 help / color / mirror / code / Atom feed
From: Keir Mierle <mierle@gmail.com>
To: zsh-workers@sunsite.dk
Subject: Implementation of simple newuser module (how to start?)
Date: Sun, 17 Jul 2005 16:16:28 -0400	[thread overview]
Message-ID: <ef5675f3050717131624a4aad7@mail.gmail.com> (raw)

It appears there is some consesus on how we can start making zsh more
usable. The idea of a 'newuser' module is great; there's tons of
things we could put in to make it easy for new user while not
frustrating zsh veterans.

I know absolutely nothing about the zsh codebase, so I've started
poking around. Now, in the interest in maximizing the amount of work I
get done while minimizing the amount of time I spend (because I don't
have much time to spend on open source stuff), could the list give me
a brief synopsis of what files I should be looking at, and what files
I should create?

To start, I was thinking of just creating a zsh script to walk the
user through setting up their prompt, turning on completion, and
telling them about autocd and a couple other options.

New idea: Create a 'tips' module that is disabled by default, but
during the newuser tutorial/setup phase, the user can choose to turn
on tips. Tips are very useful because the information is presented one
bit at a time, so users are more likely to remember it. I find startup
tips annoying with GUI programs, because I can usually discover
whatever it is the tip says without any docs just by clicking around,
but for obvious reasons this isn't the case with ZSH, making it an
excellent candidate for tips.

Thanks again,
Keir


             reply	other threads:[~2005-07-17 20:16 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-17 20:16 Keir Mierle [this message]
2005-07-18 10:13 ` Peter Stephenson
2005-07-20 14:01 ` PATCH: " Peter Stephenson
2005-07-20 18:04   ` Peter Stephenson
2005-07-23  5:10     ` Bart Schaefer
2005-07-25  9:36       ` Peter Stephenson
2005-07-26 10:21         ` Peter Stephenson
2005-07-26 14:12           ` Bart Schaefer
2005-07-26 15:08             ` 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=ef5675f3050717131624a4aad7@mail.gmail.com \
    --to=mierle@gmail.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).