Re: Do have programs have poor documentation? (was ... Re: Why? -- "A Modest Proposal")
On Monday, January 02, 2017 12:01:33 PM David Wright wrote:
> On Mon 02 Jan 2017 at 11:19:21 (-0500), rhkramer@gmail.com wrote:
> > On Monday, January 02, 2017 09:41:07 AM David Wright wrote:
> > > I have no problem navigating them. I usually consult them with the
> > > function
> > >
> > > $ info --output=/dev/stdout --subnodes "$1" | less
> > >
> > > which works well with PageUp/Dn.
> >
> > Nice, thanks!
> >
> > It seems that to get info for a specific command / subject, add the
> > command after info, i.e.:
> >
> > $ info <command> --output=/dev/stdout --subnodes "$1" | less
> >
> > E.g.:
> >
> > $ info ls --output=/dev/stdout --subnodes "$1" | less
>
> Actually the "$1" (the bash function's argument) does that task.
> If you didn't want the piping into less, you could get away
> with just an alias.
Ok, thinking slow (or reading carelessly) today. At first I couldn't figure out
why the $1, then assumed you ran it as a script, but now I see--just put ls in
place of "$ls".
> BTW I did run my function with wheezy to get the statistics for Gene,
> and noticed that I should really be throwing /dev/stderr in the bit
> bucket, ie add 2>/dev/null to the command to suppress lines like
> info: Writing node (coreutils.info.gz)Sorting the output...
> which temporarily mess up less's paging.
Reply to: