zsh-users
 help / color / mirror / code / Atom feed
From: zzapper <zsh@rayninfo.co.uk>
To: Peter Stephenson <p.w.stephenson@ntlworld.com>, zsh-users@zsh.org
Subject: Re: Using history / fc for case-insensitive pattern matching
Date: Tue, 22 Feb 2022 13:07:47 +0000	[thread overview]
Message-ID: <40c24ebc-56c0-a50c-eb8f-28c57cb80c04@rayninfo.co.uk> (raw)
In-Reply-To: <1117602475.939955.1645525125795@mail2.virginmedia.com>


On 22/02/2022 10:18, Peter Stephenson wrote:
>> To answer my own question: with fc any number range eg first last
>> should/must be the last
> Would this be a little clearer?  History (pun intended) shows that
> making the docs more verbose doesn't mean people necessarily find
> them clearer, but I think they are particularly terse at this point.
>
> pws

Peter you made me laugh out loud when you used the word 'terse'

I often find I understand documentation AFTER I have actually found out 
how to do something LOL (especially assembling flat-pack furniture).

But as you say there is trade-off between verbosity which people may not 
read and simplicity.

In this case however had I really invested in understanding the existing 
fc man page I would spared myself considerable grief.

Isn't there an adage something like '6 hours of coding and testing saves 
1 hour of studying the documentation'?

zzapper



      reply	other threads:[~2022-02-22 13:08 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-21 17:43 Zach Riggle
2022-02-21 21:01 ` Mikael Magnusson
2022-02-22  9:09   ` zzapper
2022-02-22  9:27     ` Peter Stephenson
2022-02-22  9:39       ` zzapper
2022-02-22  9:47         ` zzapper
2022-02-22 10:18           ` Peter Stephenson
2022-02-22 13:07             ` zzapper [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=40c24ebc-56c0-a50c-eb8f-28c57cb80c04@rayninfo.co.uk \
    --to=zsh@rayninfo.co.uk \
    --cc=p.w.stephenson@ntlworld.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).