On 29.10.18 10:58, David Wright wrote:
> On Sat 27 Oct 2018 at 09:19:15 (+0100), mick crane wrote:
> > I made the mistake of printing out man bash once. It's really, really long
>
> Some of the longer man pages (eg bash, fvwm, video programs) are
> rather unmanageable when just presented as flat
On 2018-10-29, Michael Stone wrote:
>
> TL;DR: man pages referencing info pages which are just man pages
> shouldn't be a thing anymore.
>
>
Those countless legions of info-page junkies (and the Philadelphia
lawyers who've oozed from the woodwork once more to litigate this gnat
up the wazoo)
On Mon, Oct 29, 2018 at 08:57:50PM +, Brian wrote:
On Mon 29 Oct 2018 at 16:27:13 -0400, Michael Stone wrote:
On Mon, Oct 29, 2018 at 10:20:30AM -0500, David Wright wrote:
> What Brian asked for is an example of a man page that ends with
> "The full documentation for foo is maintained as a
On Mon 29 Oct 2018 at 16:27:13 -0400, Michael Stone wrote:
> On Mon, Oct 29, 2018 at 10:20:30AM -0500, David Wright wrote:
> > What Brian asked for is an example of a man page that ends with
> > "The full documentation for foo is maintained as a Texinfo manual"
> > but the info foo output has
On Mon, Oct 29, 2018 at 10:20:30AM -0500, David Wright wrote:
What Brian asked for is an example of a man page that ends with
"The full documentation for foo is maintained as a Texinfo manual"
but the info foo output has no more information than man foo.
This used to be more of a problem
On Mon 29 Oct 2018 at 10:20:30 -0500, David Wright wrote:
> On Mon 29 Oct 2018 at 17:39:13 (+1100), Erik Christiansen wrote:
> > On 26.10.18 22:39, Brian wrote:
> > > On Fri 26 Oct 2018 at 15:13:20 -0500, Dennis Wicks wrote:
> > > > I agree, and I have found a lot of info "complete manual"s
> > >
On Sat 27 Oct 2018 at 09:19:15 (+0100), mick crane wrote:
> On 2018-10-26 19:17, Brian wrote:
> > {plain text fine -- HTML *NOT* needed} is MUCH more functional.
> > >
> > > Agreed, a good man page is the best. I've no clue why there
> > > seems to be
> > > an aversion to a man page that
On Mon 29 Oct 2018 at 17:39:13 (+1100), Erik Christiansen wrote:
> On 26.10.18 22:39, Brian wrote:
> > On Fri 26 Oct 2018 at 15:13:20 -0500, Dennis Wicks wrote:
> > > I agree, and I have found a lot of info "complete manual"s
> > > to be exactly like the man page!
> >
> > Please give an example.
On 26.10.18 22:39, Brian wrote:
> On Fri 26 Oct 2018 at 15:13:20 -0500, Dennis Wicks wrote:
> > I agree, and I have found a lot of info "complete manual"s
> > to be exactly like the man page!
>
> Please give an example.
Anyone who has tried info a number of times, in the hope of finding a
bit
On 26.10.18 19:17, Brian wrote:
> On Fri 26 Oct 2018 at 13:20:36 -0400, Gene Heskett wrote:
> > Agreed, a good man page is the best. I've no clue why there seems to be
> > an aversion to a man page that has to be scrolled to read it all. All of
> > us have up/down arrows on our keyboards, and
On 26.10.18 13:20, Gene Heskett wrote:
> On Friday 26 October 2018 10:41:54 Richard Owlett wrote:
> > 1. I don't want to install unneeded packages just to find out whether
> > or not the package might be useful.
> > 2. The info output has an annoying format. A browser acceptable format
> >
Thanks -- two comments below!
On Saturday, October 27, 2018 05:04:37 AM Curt wrote:
> On 2018-10-27, rhkra...@gmail.com wrote:
> > On Friday, October 26, 2018 06:10:13 PM Brian wrote:
> >> On Fri 26 Oct 2018 at 18:02:39 -0400, rhkra...@gmail.com wrote:
> >> > It's probably been 15 years since I
On 2018-10-27, rhkra...@gmail.com wrote:
> On Friday, October 26, 2018 06:10:13 PM Brian wrote:
>> On Fri 26 Oct 2018 at 18:02:39 -0400, rhkra...@gmail.com wrote:
>> > It's probably been 15 years since I bothered looking at an info page --
>> > maybe there are no more duplicate man and info pages
On 2018-10-26 19:17, Brian wrote:
> {plain text fine -- HTML *NOT* needed} is MUCH more functional.
Agreed, a good man page is the best. I've no clue why there seems to
be
an aversion to a man page that has to be scrolled to read it all. All
of
us have up/down arrows on our keyboards,
nd
inside the paper file/envelope.
> *Are online copies of textinfo content available?*
2) It also helps if you avoid spelling errors in crucial words in your subject.
On Fri 26 Oct 2018 at 10:46:12 (-0500), Richard Owlett wrote:
> *Are online copies of textinfo content available?*
>
> Many man pages end with:
> > The full documentation for Ed is maintained as a Texinfo manual. If the
> > info > and XYZ programs are properly installed a
On Friday, October 26, 2018 06:10:13 PM Brian wrote:
> On Fri 26 Oct 2018 at 18:02:39 -0400, rhkra...@gmail.com wrote:
> > It's probably been 15 years since I bothered looking at an info page --
> > maybe there are no more duplicate man and info pages -- but I don't
> > believe that.
>
> You can
rhkramer writes:
> I'm not the OP, and I don't have an example at hand, but I can vouch
> for the same thing, man pages and info containing the same
> information, modulo looking a little different.
Not always.
--
John Hasler
jhas...@newsguy.com
Elmwood, WI USA
On Sat, 27 Oct 2018 at 06:50, wrote:
> On Friday, October 26, 2018 02:22:32 PM Greg Wooledge wrote:
> > Use the "type" command to see.
> >
> > wooledg:~$ type cd
> > cd is a shell builtin
> > wooledg:~$ type ls
> > ls is hashed (/bin/ls)
>
> Ahh, wonderful -- thank you!
See also 'help type' for
On Fri 26 Oct 2018 at 18:02:39 -0400, rhkra...@gmail.com wrote:
> On Friday, October 26, 2018 05:39:55 PM Brian wrote:
> > On Fri 26 Oct 2018 at 15:13:20 -0500, Dennis Wicks wrote:
> > > Richard Owlett wrote on 10/26/18 9:41 AM:
> > > > Many man pages end with:
> > > >> The full documentation for
On Friday, October 26, 2018 05:39:55 PM Brian wrote:
> On Fri 26 Oct 2018 at 15:13:20 -0500, Dennis Wicks wrote:
> > Richard Owlett wrote on 10/26/18 9:41 AM:
> > > Many man pages end with:
> > >> The full documentation for Ed is maintained as a Texinfo
> > >> manual. If the info > and XYZ
On Fri 26 Oct 2018 at 15:13:20 -0500, Dennis Wicks wrote:
>
>
> Richard Owlett wrote on 10/26/18 9:41 AM:
> > Many man pages end with:
> >> The full documentation for Ed is maintained as a Texinfo
> >> manual. If the info > and XYZ programs are properly
> >> installed at your site, the command
Dennis Wicks writes:
> Another thing you can try is
> sudo apt show XYZ
> That will give you a bunch of info including a few lines of
> description. Usually enough to decide whether to pursue that
> package further.
That will give you the complete package description (and sudo is not
Greg Wooledge wrote on 10/26/18 3:16 PM:
> On Fri, Oct 26, 2018 at 03:13:20PM -0500, Dennis Wicks wrote:
>> sudo apt show XYZ
>
> For the record, you don't need to be root to use apt show, or apt-cache show.
>
>
>
Right you are! I guess it has become such a habit I just do
it
On Fri, Oct 26, 2018 at 03:13:20PM -0500, Dennis Wicks wrote:
> sudo apt show XYZ
For the record, you don't need to be root to use apt show, or apt-cache show.
Richard Owlett wrote on 10/26/18 9:41 AM:
> Many man pages end with:
>> The full documentation for Ed is maintained as a Texinfo
>> manual. If the info > and XYZ programs are properly
>> installed at your site, the command
>>
>> info XYZ
>>
>> should give you access to the complete manual.
On Friday, October 26, 2018 02:22:32 PM Greg Wooledge wrote:
> On Fri, Oct 26, 2018 at 02:12:29PM -0400, rhkra...@gmail.com wrote:
> > Just to chime in, my problem with the bash man page is knowing whether a
> > given command is a bash built-in or external command -- if built-in,
> > I'll find
On Fri, Oct 26, 2018 at 02:12:29PM -0400, rhkra...@gmail.com wrote:
> Just to chime in, my problem with the bash man page is knowing whether a
> given
> command is a bash built-in or external command -- if built-in, I'll find
> information within the man page.
>
> I usually first look for a
On Fri 26 Oct 2018 at 13:20:36 -0400, Gene Heskett wrote:
> On Friday 26 October 2018 10:41:54 Richard Owlett wrote:
>
> > Many man pages end with:
> > > The full documentation for Ed is maintained as a Texinfo manual. If
> > > the info > and XYZ programs are properly installed at your site, the
On Friday, October 26, 2018 01:20:36 PM Gene Heskett wrote:
> Agreed, a good man page is the best. I've no clue why there seems to be
> an aversion to a man page that has to be scrolled to read it all. All of
> us have up/down arrows on our keyboards, and 99% have a mouse wheel, so
> there is no
On Friday 26 October 2018 10:41:54 Richard Owlett wrote:
> Many man pages end with:
> > The full documentation for Ed is maintained as a Texinfo manual. If
> > the info > and XYZ programs are properly installed at your site, the
> > command
> >
> > info XYZ
> >
> > should give you access to
On Fri, Oct 26, 2018 at 10:46:12AM -0500, Richard Owlett wrote:
I posted this question to debian-user@lists.debian.org .
The replies totally ignored my primary question and reason I asked
[emphasized in this copy].
You seemingly ignored answers which addressed it.
Side question:
Could I have
On Fri 26 Oct 2018 at 10:46:12 -0500, Richard Owlett wrote:
> *Are online copies of textinfo content available?*
https://www.gnu.org/manual/manual.en.html
--
Brian.
*Are online copies of textinfo content available?*
Many man pages end with:
The full documentation for Ed is maintained as a Texinfo manual. If the info >
and XYZ programs are properly installed at your site, the command
info XYZ
should give you access to the complete manual.
I h
On Fri 26 Oct 2018 at 09:41:54 (-0500), Richard Owlett wrote:
> Many man pages end with:
> > The full documentation for Ed is maintained as a Texinfo manual. If the
> > info > and XYZ programs are properly installed at your site, the command
> >
> > info XYZ
> >
> > should give you access
On Fri, Oct 26, 2018 at 09:41:54AM -0500, Richard Owlett wrote:
Many man pages end with:
The full documentation for Ed is maintained as a Texinfo manual. If the info >
and XYZ programs are properly installed at your site, the command
info XYZ
should give you access to the complete manual.
On Fri 26 Oct 2018 at 09:41:54 -0500, Richard Owlett wrote:
> Many man pages end with:
> > The full documentation for Ed is maintained as a Texinfo manual. If the
> > info > and XYZ programs are properly installed at your site, the command
> >
> > info XYZ
> >
> > should give you access to
Many man pages end with:
The full documentation for Ed is maintained as a Texinfo manual. If the info >
and XYZ programs are properly installed at your site, the command
info XYZ
should give you access to the complete manual.
I have problems with that.
1. I don't want to install
38 matches
Mail list logo
