From: Wayne Davison <wayned@users.sourceforge.net>
To: Zsh Workers <zsh-workers@sunsite.dk>
Subject: Re: Automatic hash -d
Date: Fri, 13 Apr 2001 01:01:34 -0700 (PDT) [thread overview]
Message-ID: <Pine.LNX.4.30.0104130100130.8432-100000@phong.blorf.net> (raw)
In-Reply-To: <1010413050904.ZM1154@candle.brasslantern.com>
On Fri, 13 Apr 2001, Bart Schaefer wrote:
> Index: Completion/Unix/Type/_path_files
I applied both of your changes to _path_files, and things are working
very nicely now. I'll let you know if I encounter any problems.
..wayne..
next prev parent reply other threads:[~2001-04-13 8:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-13 2:08 Wayne Davison
2001-04-13 2:30 ` "keep-prefix true" feature request Wayne Davison
2001-04-13 4:50 ` Bart Schaefer
2001-04-13 5:09 ` Automatic hash -d Bart Schaefer
2001-04-13 8:01 ` Wayne Davison [this message]
2001-04-13 15:38 ` Bart Schaefer
2001-04-13 16:47 ` Bart Schaefer
2001-04-17 9:04 ` Sven Wischnowsky
2001-04-18 5:56 ` PATCH (?): " Bart Schaefer
2001-04-18 8:29 ` Sven Wischnowsky
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=Pine.LNX.4.30.0104130100130.8432-100000@phong.blorf.net \
--to=wayned@users.sourceforge.net \
--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).