From: Bart Schaefer <schaefer@brasslantern.com>
To: Zsh User <zsh-users@sunsite.dk>
Subject: Re: dirstack history: loving zsh, crashing zsh...
Date: Sun, 05 Mar 2006 01:19:47 -0800 [thread overview]
Message-ID: <060305011947.ZM7258@torch.brasslantern.com> (raw)
In-Reply-To: <20060302175252.GA31734@let.rug.nl>
On Mar 2, 6:52pm, Francisco Borges wrote:
}
} % typeset -U dirstack
}
} and the shell crashed. (I kid you not!)
Since no one else has pointed it out yet, the Right Thing here is
setopt pushd_ignore_dups
dirstack=( ${(u)$(< ~/.zdirs)} )
} OR you guys are now going to say: "Don't you know you're not supposed
} to use typeset with dirstack!!"
You aren't, but the shell isn't supposed to crash, either.
next prev parent reply other threads:[~2006-03-05 9:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-02 17:52 Francisco Borges
2006-03-02 18:07 ` William Scott
2006-03-05 9:19 ` Bart Schaefer [this message]
2006-03-06 13:01 ` [zsh] " Francisco Borges
2006-03-06 16:51 ` Bart Schaefer
2006-03-06 18:26 ` [zsh] " Francisco Borges
2006-03-07 3:54 ` Bart Schaefer
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=060305011947.ZM7258@torch.brasslantern.com \
--to=schaefer@brasslantern.com \
--cc=zsh-users@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).