zsh-users
 help / color / mirror / code / Atom feed
From: Bart Schaefer <schaefer@brasslantern.com>
To: zsh-users@zsh.org
Subject: Re: cd - not expanding to dirs
Date: Mon, 19 Nov 2012 19:48:06 -0800	[thread overview]
Message-ID: <121119194806.ZM4576@torch.brasslantern.com> (raw)
In-Reply-To: <XnsA110E0A599017zzappergmailcom@80.91.229.13>

On Nov 19, 10:05pm, zzapper wrote:
}
} But how should I have known that "cd -" depended on [compinit] ?

Osmosis?

More seriously, attempting to answer this question (and similar ones about
how to introduce novice users to the zsh feature set) is what led to the
creation of the zsh/newuser module and zsh-newuser-install function.

Ideally the first time you ran the shell you should have been prompted by
the newuser subsystem to initialize completion and various other setup.
If you aren't the first root user, or the OS packager includes a default
setup for root, then you miss out on this.

} How should I have approached searching the doc? 

In this case it's less how you should have approached searching it than
how you should have approached browsing it.

The third section of the documentation is entitled "Roadmap".  There is
a subsection therein called "Completion".  The second paragraph of that
section says:

  Zsh has two completion systems, an old, so called compctl completion
  (named after the builtin command that serves as its complete and only
  user interface), and a new one, referred to as compsys, organized as
  library of builtin and user-defined functions.  The two systems differ
  in their interface for specifying the completion behavior.  The new
  system is more customizable and is supplied with completions for many
  commonly used commands; it is therefore to be preferred.

  The completion system must be enabled explicitly when the shell starts.
  For more information see Completion System.

Those last two words are a link to the twentieth (!) section, which
rambles a bit about contexts and styles and dispatchers, and then moves
on with a section "Initialization" which explains compinit.


  reply	other threads:[~2012-11-20  3:48 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-19 17:43 zzapper
2012-11-19 21:35 ` Bart Schaefer
2012-11-19 22:05   ` zzapper
2012-11-20  3:48     ` Bart Schaefer [this message]
2012-11-20 13:50       ` zzapper
2012-11-20 13:46   ` zzapper

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=121119194806.ZM4576@torch.brasslantern.com \
    --to=schaefer@brasslantern.com \
    --cc=zsh-users@zsh.org \
    /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).