From: Roman Perepelitsa <roman.perepelitsa@gmail.com>
To: dominik.vogt@gmx.de, Zsh Users <zsh-users@zsh.org>
Subject: Re: Where do these completions come from?
Date: Fri, 15 Oct 2021 21:13:26 +0200 [thread overview]
Message-ID: <CAN=4vMoadZvRj1=uS47Px8zDaU7DxPSkmd77205kGhh1z8NNpw@mail.gmail.com> (raw)
In-Reply-To: <20211015185603.GA8362@gmx.de>
On Fri, Oct 15, 2021 at 8:59 PM Dominik Vogt <dominik.vogt@gmx.de> wrote:
>
> On Fri, Oct 15, 2021 at 08:46:27PM +0200, Roman Perepelitsa wrote:
> > On Fri, Oct 15, 2021 at 8:43 PM Dominik Vogt <dominik.vogt@gmx.de> wrote:
> > >
> > > I accidentally hit "d<tab>" and a list of things got displayed
> > > (menu completion), including
> > >
> > > dis_aliases
> > > dis_builtins
> > > dis_functions
> > > dis_functions_source
> > > dis_galiases
> > > dis_patchars
> >
> > These are parameters. They come from the zsh/parameter module. See
> > `man zshmodules`.
>
> Okay, understood. But why is it useful to expand hashtable names
> in command position?
I don't think it's useful. You can disable it:
zstyle ':completion:*:complete:-command-:*:*' tag-order \
'commands functions' -
I don't know why the default is what it is. I don't expect zsh
defaults to make sense. Why is interactive_comments disabled in
interactive shells? Why does prompt show hostname but not the current
directory? It's all for historical reasons, I guess. I do appreciate
that my shell doesn't break when I upgrade to a newer version of zsh,
so backward compatibility is a valid justification for all this.
Roman.
next prev parent reply other threads:[~2021-10-15 19:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-15 18:40 Dominik Vogt
2021-10-15 18:46 ` Roman Perepelitsa
2021-10-15 18:56 ` Dominik Vogt
2021-10-15 19:13 ` Roman Perepelitsa [this message]
2021-10-15 20:10 ` Bart Schaefer
2021-10-15 20:26 ` Dominik Vogt
2021-10-16 18:59 ` Bart Schaefer
2021-10-16 21:30 ` Dominik Vogt
2021-10-17 19:00 ` 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='CAN=4vMoadZvRj1=uS47Px8zDaU7DxPSkmd77205kGhh1z8NNpw@mail.gmail.com' \
--to=roman.perepelitsa@gmail.com \
--cc=dominik.vogt@gmx.de \
--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).