help / color / mirror / code / Atom feed
From: Thomas Lauer <thomas.lauer@virgin.net>
To: Roman Perepelitsa <roman.perepelitsa@gmail.com>
Cc: zsh-users@zsh.org
Subject: Re: completing .directories without . and ..
Date: Wed, 22 Feb 2023 13:16:58 +0000	[thread overview]
Message-ID: <j05cvh1ue63m5s0j763aatlbbub6or8nqm@tlc.com> (raw)
In-Reply-To: <CAN=4vMqCNYyyW0UZn3uV2h7zKfqvNxnp-9gLuqmN0JU0CG+bZA@mail.gmail.com>

From: Roman Perepelitsa <roman.perepelitsa@gmail.com>
Date: Tue, 21 Feb 2023 20:14:22 +0100
Subj: Re: completing .directories without . and ..
> On Tue, Feb 21, 2023 at 5:59 PM Thomas Lauer <thomas.lauer@virgin.net> wrote:
> >
> > From: Roman Perepelitsa <roman.perepelitsa@gmail.com>
> > Date: Tue, 21 Feb 2023 17:48:44 +0100
> > > See "special-dirs" in `man zshcompsys` for documentation.
> >
> > Right. I knew it was something simple but all my attempts to find that
> > simple thing were getting nowhere.
> Here's a hypothetical yet plausible way how you could've found it.
<rest snipped>

Yeah, I normally follow a similar path (at least when I've got an idea
where to look... zsh being zsh means that this is not always obvious to
a "casual" user). In this case I knew it had to be a zstyle thing but I
somehow got fixated on the search term dotdir or dot-dir (or
variations)... that probably had to do with the fruitless Google
searches I'd done before.

Anyway, I'll try harder to broaden my knowledge of how to find


  parent reply	other threads:[~2023-02-22 13:17 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-21 16:38 Thomas Lauer
2023-02-21 16:48 ` Roman Perepelitsa
2023-02-21 16:59   ` Thomas Lauer
2023-02-21 17:14     ` Ray Andrews
2023-02-21 18:09       ` Thomas Lauer
2023-02-21 19:14     ` Roman Perepelitsa
2023-02-21 21:25       ` Ray Andrews
2023-02-21 22:11       ` Bart Schaefer
2023-02-22 13:16       ` Thomas Lauer [this message]
2023-02-22 13:31         ` Thomas Lauer

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=j05cvh1ue63m5s0j763aatlbbub6or8nqm@tlc.com \
    --to=thomas.lauer@virgin.net \
    --cc=roman.perepelitsa@gmail.com \
    --cc=zsh-users@zsh.org \


* 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


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).