Message-ID: <691a3b7e@news.ausics.net> From: not@telling.you.invalid (Computer Nerd Kev) Subject: Re: My 2 favorite tools for reading Linux manual pages the easy way Newsgroups: comp.os.linux.misc References: <10f34ng$1pnvq$1@dont-email.me> <10f5dib$2crs6$2@dont-email.me> <10f5e30$2d31u$1@dont-email.me> <8ruhulx88g.ln2@Telcontar.valinor> <69179e3a@news.ausics.net> <10f8opa$385vs$7@dont-email.me> <6918f114@news.ausics.net> <10fatkf$3p4r1$4@dont-email.me> User-Agent: tin/2.6.5-20250707 ("Helmsdale") (Linux/2.4.31 (i586)) NNTP-Posting-Host: news.ausics.net Date: 17 Nov 2025 07:00:46 +1000 Organization: Ausics - https://newsgroups.ausics.net Lines: 15 X-Complaints: abuse@ausics.net Path: csiph.com!news.bbs.nz!news.ausics.net!not-for-mail Xref: csiph.com comp.os.linux.misc:77654 Lawrence D'Oliveiro wrote: > On 16 Nov 2025 07:31:00 +1000, Computer Nerd Kev wrote: >> But I see it doesn't work for "-r" anyway because that's defined with >> square brakets for the optional stream specifier: >> >> -r[:stream_specifier] fps (input/output,per-stream) > > "\s-r\b" does find a few actual uses of -r before hitting on the > definition. "^\s+-r\b" goes straight to the definition. That one works well. -- __ __ #_ < |\| |< _#