From: Thomas Lauer <firstname.lastname@example.org>
To: Ray Andrews <email@example.com>
Subject: Re: completing .directories without . and ..
Date: Tue, 21 Feb 2023 18:09:28 +0000 [thread overview]
Message-ID: <firstname.lastname@example.org> (raw)
From: Ray Andrews <email@example.com>
Date: Tue, 21 Feb 2023 09:14:29 -0800
> On 2023-02-21 08:59, Thomas Lauer wrote:
> > And googling with such terms as . or
> > .. is an exercise in futility (not to talk about stuff like -option or
> > --option).
> I whine about things like that often. The terseness of zsh syntax makes
> google searches for actual syntax often absurd. But apart from
> inside-out learning, is a solution even possible? Maybe. Meanwhile,
> thank God for this list, where you can just doff your cap and ask the
> people who know.
(Possibly future) versions of something like ChatGPT et al could well
present a solution for these things. They'd be able to discern and
understand (within certain limits) the actual semantics of what is being
asked and should, after (perhaps extensive) training, be able to deliver
relevant answers or at the very least pointers to answers.
next prev parent reply other threads:[~2023-02-21 18:10 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 [this message]
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
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 \
* 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).