From: Roman Perepelitsa <roman.perepelitsa@gmail.com>
To: Zach Riggle <zachriggle@gmail.com>
Cc: Zsh Users <zsh-users@zsh.org>
Subject: Re: Better Help Docs Searching?
Date: Sun, 1 Aug 2021 13:01:13 +0200 [thread overview]
Message-ID: <CAN=4vMoaurtxQJXvmd2SsDDRhZ74RwKmsvCbseHC9z-utdSwTA@mail.gmail.com> (raw)
In-Reply-To: <CAMP9c5m=oOwSvEaqVF62GF0=BjjMnS8fBEmbcWz9ydxqx=tvZQ@mail.gmail.com>
On Sun, Aug 1, 2021 at 12:46 PM Zach Riggle <zachriggle@gmail.com> wrote:
>
> All of that said, is there any way to easily find keywords / flags in
> either the online docs OR the man pages -- rather than having way too
> many matches for other things that mention the same word (e.g. "read"
> as mentioned above).
There might be better ways but here's how I do it.
I have this in my ~/.zshrc:
autoload -Uz run-help
unalias run-help
This allows me to type "read" in an interactive shell and press Alt+h
(aka ESC h) to open the help file for the read builtin.
Sometimes this doesn't work (for example, try it with "bindkey"). In
this case I would run `man zshall` (one page to rule them all) and
search for " read" -- note a bunch of spaces in front. If this
query has too many hits, I would use "^ {4,}read\b". I use the same
trick when searching for the description of flags in man pages. For
example, to find the description of "-z" in `man rsync`, I would first
search for " -z" because it's easy to type and then for the more
specific "^ {4,}-z\b" in case I get too many hits.
Roman.
next prev parent reply other threads:[~2021-08-01 11:02 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-01 10:44 Zach Riggle
2021-08-01 11:01 ` Roman Perepelitsa [this message]
2021-08-01 16:21 ` Mikael Magnusson
2021-08-01 16:33 ` Stephane Chazelas
2021-08-01 18:52 ` Bart Schaefer
2021-08-01 20:11 ` Ray Andrews
2021-08-03 5:45 ` Zach Riggle
2021-08-03 8:03 ` Zach Riggle
2021-08-03 8:09 ` Zach Riggle
2021-08-03 8:44 ` Peter Stephenson
2021-08-03 9:40 ` Zach Riggle
2021-08-03 9:57 ` Peter Stephenson
2021-08-03 16:47 ` Bart Schaefer
2021-08-03 11:28 ` david rayner
2021-08-05 15:31 ` Vincent Lefevre
2021-08-03 16:52 ` Bart Schaefer
2021-08-01 16:25 ` Bart Schaefer
2021-08-05 9:56 ` Vincent Lefevre
2021-08-04 6:30 ` Roman Neuhauser
2021-08-04 14:56 ` Ray Andrews
2021-08-04 16:08 ` Bart Schaefer
2021-08-05 12:00 ` Ray Andrews
2021-08-04 16:38 ` Roman Neuhauser
2021-08-04 16:05 ` Bart Schaefer
2021-08-04 16:45 ` Roman Neuhauser
2021-08-14 15:41 ` Daniel Shahaf
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='CAN=4vMoaurtxQJXvmd2SsDDRhZ74RwKmsvCbseHC9z-utdSwTA@mail.gmail.com' \
--to=roman.perepelitsa@gmail.com \
--cc=zachriggle@gmail.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).