From: Sven Wischnowsky <wischnow@informatik.hu-berlin.de>
To: zsh-workers@sunsite.auc.dk
Subject: Re: PATCH: zsh and perl
Date: Wed, 15 Nov 2000 11:56:38 +0100 (MET) [thread overview]
Message-ID: <200011151056.LAA05515@beta.informatik.hu-berlin.de> (raw)
In-Reply-To: "Bart Schaefer"'s message of Tue, 14 Nov 2000 16:10:25 +0000
Bart Schaefer wrote:
> ...
>
> Any suggestions for how to avoid the chpwd problem?
I'm sure I'm missing something, but... why not just avoid the cd
altogether? Something like
new_pms=( $libdir/{[a-Z]*/***/,}*.pm~*blib* )
new_pms=( "${(@)new_pms#$libdir/}" )
probably testing if $libdir is non-empty before that...
Bye
Sven
--
Sven Wischnowsky wischnow@informatik.hu-berlin.de
next reply other threads:[~2000-11-15 10:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-15 10:56 Sven Wischnowsky [this message]
2000-11-15 16:03 ` Bart Schaefer
2000-11-16 12:18 ` Adam Spiers
-- strict thread matches above, loose matches on Subject: below --
2000-11-14 12:47 Paul Johnson
2000-11-14 16:10 ` 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=200011151056.LAA05515@beta.informatik.hu-berlin.de \
--to=wischnow@informatik.hu-berlin.de \
--cc=zsh-workers@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).