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

From: Thomas Lauer <thomas.lauer@virgin.net>
Date: Wed, 22 Feb 2023 13:16:58 +0000
> In this case I knew it had to be a zstyle thing

Let me add another observation. There are areas within zsh and the docs
where I (perhaps falsely) believe I have a good idea how things work or
hang together. And then there are a couple other bits which to my mind
are almost beyond comprehension and which I approach with, shall we say,
some apprehension. The completion system is one of those and I readily
admit that I could and should invest a good chunk of time to try to get
a handle on that.

Many decades ago, I bought a 6502 microcomputer and big blue book about
6502 assembly language. I knew nothing about computers, let alone
machine language, and I read that book perhaps five times until I began
to get a glimmer of an idea what this stuff was all about. I was on a
long and boring holiday then, so time was no problem:-) and so I read it
again and still again until it started to make sense.


      reply	other threads:[~2023-02-22 13:31 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
2023-02-22 13:31         ` Thomas Lauer [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:

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

  git send-email \
    --in-reply-to=1i5cvh1v1jv7birvu7p9sqhuqjkaon5vnh@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).