zsh-users
 help / color / mirror / code / Atom feed
From: "Peter Slížik" <peter.slizik@gmail.com>
To: Zsh Users <zsh-users@zsh.org>
Subject: Re: <Tab> completion does not insert a slash
Date: Tue, 17 Aug 2021 10:57:46 +0200	[thread overview]
Message-ID: <CAC-uhUD-q0N1msuhzP10tUNEg34Ti54GEAN=j5zWYAuSWBW+tg@mail.gmail.com> (raw)
In-Reply-To: <CAH+w=7aC2YDym40K3rY=OnFVjSjqYW29EY+U3trXyVdo0J0FFg@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 832 bytes --]

> The descriptions here are showing you every place from which a
> completion string was gathered, but then all the completions are
> lumped together at the end.  (That is, you get all the descriptions,
> and then all the completions.)  If you actually want the completion
> strings to appear immediately after each description, you have to add
>
> zstyle ':completion:*' group-name ""
>

My bad. I used to have this on, but later turned it off in an attempt to
minimize the amount of configuration changes and forgot about it.

I think it's time to close this thread. The analysis of Ctrl-X ? logs would
take (I guess) a few days of studying the inner workings of the completion
system and I cannot afford such a time allocation at the moment. I'd like
to thank all who answered and namely Bart for the advice and patience.

Peter

[-- Attachment #2: Type: text/html, Size: 1134 bytes --]

      reply	other threads:[~2021-08-17  8:59 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-04 15:02 Peter Slížik
2021-08-04 15:45 ` Bart Schaefer
2021-08-04 16:49   ` Peter Slížik
2021-08-04 17:26     ` Bart Schaefer
2021-08-11 20:03       ` Peter Slížik
2021-08-11 20:23         ` Peter Slížik
2021-08-11 22:20           ` Bart Schaefer
2021-08-16 21:39             ` Peter Slížik
2021-08-16 21:41               ` Peter Slížik
2021-08-16 22:17               ` Bart Schaefer
2021-08-17  8:57                 ` Peter Slížik [this message]

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='CAC-uhUD-q0N1msuhzP10tUNEg34Ti54GEAN=j5zWYAuSWBW+tg@mail.gmail.com' \
    --to=peter.slizik@gmail.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).