From: Daniel Shahaf <d.s@daniel.shahaf.name>
To: zsh-users@zsh.org
Subject: Re: Most minimal configuration challenge
Date: Fri, 2 Sep 2022 10:36:48 +0000 [thread overview]
Message-ID: <20220902103648.GM5920@tarpaulin.shahaf.local2> (raw)
In-Reply-To: <CAMP44s2NjmLSmrNUBnd_zh4_-NtpUzU0uZFeMq7HMnFuMMVr9w@mail.gmail.com>
Felipe Contreras wrote on Thu, Sep 01, 2022 at 20:49:52 -0500:
> On Thu, Sep 1, 2022 at 8:27 PM Lawrence Velázquez <larryv@zsh.org> wrote:
> > On Wed, Aug 31, 2022, at 10:17 AM, Ray Andrews wrote:
> > > Experts have the mind of experts. So the above no doubt makes
> > > perfect sense to the expert who wrote it and already understands
> > > it, but is useless to me.
> >
> > I think this is pretty harsh toward Daniel. I have no doubt he
> > could have written a more verbose and comprehensive explanation in
> > a paragraph or two, but I wouldn't have been surprised if you'd
> > objected to its wordiness.
>
There's no easy way to explain zstyle in a sentence since it has so many
moving parts (keys, values, contexts, context patterns).
> It's not either or. I constantly try to put myself in the shoes of
> newcomers, and sometimes an explanation I give is deemed not clear
> enough. Does that mean I failed and I'm stupid? No, it's just
> feedback, I can try another one.
>
> People who are not constantly being subject to criticism often think
> it's something negative, but it isn't, it's just an opportunity to try
> something better.
>
> Ultimately the people who should judge prose meant for newcomers, are
> newcomers. If they say it isn't clear, then it isn't clear.
It wasn't meant to be clear. It was meant to be a summary of the
answer, so that:
1. Anyone who RTFM'd following my post would know whether they were
reading the right part of the docs.
2. Anyone who /already knew/ the topic would know they could skip that
pointer to the docs.
3. Readers (including lurkers) would get a fishing rod rather than a fish.
next prev parent reply other threads:[~2022-09-02 10:38 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-27 4:30 Felipe Contreras
2022-08-27 16:10 ` Daniel Shahaf
2022-08-27 19:32 ` Vincent Bernat
2022-08-27 20:04 ` Lawrence Velázquez
2022-08-27 23:53 ` Ray Andrews
2022-08-28 7:53 ` zzapper
2022-08-28 10:30 ` Daniel Shahaf
2022-08-28 13:59 ` Ray Andrews
2022-08-28 18:29 ` Daniel Shahaf
2022-08-31 9:28 ` Vincent Lefevre
2022-08-31 14:17 ` Ray Andrews
2022-09-01 21:52 ` Felipe Contreras
2022-09-02 1:41 ` Lawrence Velázquez
2022-09-02 1:26 ` Lawrence Velázquez
2022-09-02 1:49 ` Felipe Contreras
2022-09-02 5:40 ` Lawrence Velázquez
2022-09-02 7:38 ` Felipe Contreras
2022-09-02 10:36 ` Daniel Shahaf [this message]
2022-09-02 14:26 ` Ray Andrews
2022-09-04 7:13 ` Daniel Shahaf
2022-09-04 16:30 ` Ray Andrews
2022-09-02 10:39 ` [PATCH] zstyle: Correct and expand docs (was: Re: Most minimal configuration challenge) Daniel Shahaf
2022-09-02 15:05 ` Bart Schaefer
2022-09-04 6:51 ` Daniel Shahaf
2022-09-02 13:55 ` Most minimal configuration challenge Ray Andrews
2022-09-04 7:21 ` Daniel Shahaf
2022-09-04 16:34 ` Ray Andrews
2022-09-02 13:32 ` Ray Andrews
2022-09-04 7:28 ` Daniel Shahaf
2022-09-02 9:53 ` Daniel Shahaf
2022-09-02 9:26 ` Daniel Shahaf
2022-09-02 14:44 ` Vincent Lefevre
2022-09-04 6:42 ` Daniel Shahaf
2022-09-05 9:47 ` Vincent Lefevre
2022-09-12 8:59 ` Daniel Shahaf
2022-08-28 18:58 ` Bart Schaefer
2022-08-28 19:23 ` Felipe Contreras
2022-08-28 19:35 ` Ray Andrews
2022-08-28 18:57 ` Felipe Contreras
2022-09-02 1:36 ` Vincent Lefevre
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=20220902103648.GM5920@tarpaulin.shahaf.local2 \
--to=d.s@daniel.shahaf.name \
--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).