zsh-users
 help / color / mirror / code / Atom feed
From: Bruce Stephens <bruce@cenderis.demon.co.uk>
To: zsh-users@sunsite.auc.dk
Subject: Re: Zsh showoff
Date: 14 Oct 1999 21:38:56 +0100	[thread overview]
Message-ID: <87wvspllsv.fsf@cenderis.demon.co.uk> (raw)
In-Reply-To: Claus Alboege's message of "Thu, 14 Oct 1999 11:06:46 +0200"

Claus Alboege <tractrix@control.auc.dk> writes:

> I'm rather new to the zsh, and wonder if someone would show me some
> .zsh* files, that could show some of the nice (and more spectacular)
> features of zsh. Right now I don't care about memory footprint, so
> everything is welcome.

The default behaviour is pretty good.  Here's approximately what I
have in .zshrc:


PS1="%n%# "
RPROMPT="%~"
[[ $TERM = "xterm" ]] && stty pass8 -ixon && bindkey -me
setopt autopushd autocd autolist
setopt autoparamkeys autoremoveslash cdablevars
setopt completeinword correctall correct equals
setopt extendedglob magicequalsubst histignoredups
setopt numericglobsort pushdignoredups

ttyctl -u


There's some completion stuff, but that's all automatically added in
3.1.6.

I'm not sure what would be obvious (other than the current directory
at the right hand side, from RPROMPT, obviously).

autopushcd means that every change directory command acts as a pushd
(so you can use popd to get back to previous directories, which I find
convenient).  

autocd means you can change to directories just by naming them (i.e.,
you can say things like "../../../src", omitting the command "cd").

Probably the one I use most is extendedglob.  All C files underneath
the current working directory modified in the last day, "**/*.c(m-1)",
and stuff.  The ~ operator is handy, too: all files except the C
files, "*~*.c".


  reply	other threads:[~1999-10-14 20:39 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-10-14  9:06 Claus Alboege
1999-10-14 20:38 ` Bruce Stephens [this message]
1999-11-14  1:24   ` Adam Spiers
1999-12-27 14:32 ` Larry P . Schrof

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=87wvspllsv.fsf@cenderis.demon.co.uk \
    --to=bruce@cenderis.demon.co.uk \
    --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).