From: Peter Stephenson <p.stephenson@samsung.com>
To: <zsh-users@zsh.org>
Subject: Re: completion of filenames
Date: Tue, 10 Dec 2019 17:16:13 +0000 [thread overview]
Message-ID: <1575998173.4447.6.camel@samsung.com> (raw)
In-Reply-To: <eabc8850-c59f-767e-02be-5681a782cc34@eastlink.ca>
On Tue, 2019-12-10 at 08:59 -0800, Ray Andrews wrote:
> On 2019-12-10 8:30 a.m., Peter Stephenson wrote:
> >
> >
> > Suffix aliases are already handled. So if it's a file in the current directory,
> > you should find typing ./<tab> completes files with a suffix alias defined.
> >
> > pws
> >
> Doesn't work. This could be something I've botched up myself.
Try ^x h and you should see something like (warning: these are long
lines I've not attempted to wrap myself so anything could happen):
tags in context :completion::complete:-command-::
commands executables builtins functions aliases suffix-aliases reserved-words jobs parameters parameters (_command_names _autocd)
commands (_path_commands _command_names _autocd)
globbed-files (_files _command_names _autocd)
directories (_files _command_names _autocd)
all-files (_files _command_names _autocd)
jobs (_jobs _command_names _autocd)
parameters (_parameters _command_names _autocd)
The "suffix-aliases" is obviously relevant here. As you can see it's
handled by _command_names. (Well, OK, it might be handled by _autocd
but it isn't.) If you look in there you'll see it's calling
_suffix_alias_files. I don't see any obvious styles to get in the way.
pws
next prev parent reply other threads:[~2019-12-10 17:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20191210161919epcas1p2c60b547299b6425434345c4f26071643@epcas1p2.samsung.com>
2019-12-10 16:17 ` Ray Andrews
2019-12-10 16:30 ` Peter Stephenson
2019-12-10 16:59 ` Ray Andrews
2019-12-10 17:16 ` Peter Stephenson [this message]
2019-12-10 17:45 ` Ray Andrews
2019-12-13 15:59 ` Ray Andrews
2019-12-13 16:24 ` Peter Stephenson
2019-12-13 17:06 ` Ray Andrews
2019-12-13 19:46 ` Bart Schaefer
2019-12-13 21:10 ` Ray Andrews
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=1575998173.4447.6.camel@samsung.com \
--to=p.stephenson@samsung.com \
--cc=zsh-users@zsh.org \
/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).