From: "Bart Schaefer" <schaefer@candle.brasslantern.com>
To: Sven Wischnowsky <wischnow@informatik.hu-berlin.de>,
zsh-workers@sunsite.dk
Subject: Re: .. completion
Date: Mon, 18 Jun 2001 09:18:49 +0000 [thread overview]
Message-ID: <1010618091849.ZM27654@candle.brasslantern.com> (raw)
In-Reply-To: <200106180746.JAA11360@beta.informatik.hu-berlin.de>
On Jun 18, 9:46am, Sven Wischnowsky wrote:
} Subject: Re: .. completion
}
} [moved to -workers]
}
} Bart Schaefer wrote:
}
} > ...
} >
} > In _path_files, the special-dirs style is looked up only as a string, but
} > the documentation says it may be either a string or a boolean.
So the handling of special-dirs is really done in the C code for compfiles?
} > However, in _files, _path_files is always called with -g option, so the
} > special-dirs style doesn't work at all for _files.
}
} Eh? Works for me. And _files can call _path_files without the -g
} option, in line 80.
I'm sorry, I must be mis-reading the difference between
_path_files -g "$pat" "$opts[@]" "$expl[@]" && ret=0
and
_path_files "$expl[@]" -g "$pat" "$opts[@]" && ret=0
In any case, special-dirs doesn't work for me. I finally narrowed it
down to this:
zstyle ':completion:*' file-sort modification
Why should the file-sort style have any effect at all on special-dirs?
--
Bart Schaefer Brass Lantern Enterprises
http://www.well.com/user/barts http://www.brasslantern.com
Zsh: http://www.zsh.org | PHPerl Project: http://phperl.sourceforge.net
next prev parent reply other threads:[~2001-06-18 9:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1010616204004.ZM5912@candle.brasslantern.com>
2001-06-18 7:46 ` Sven Wischnowsky
2001-06-18 9:18 ` Bart Schaefer [this message]
2001-06-18 9:44 ` 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=1010618091849.ZM27654@candle.brasslantern.com \
--to=schaefer@candle.brasslantern.com \
--cc=wischnow@informatik.hu-berlin.de \
--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).