unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: "Robert Thorpe" <rthorpe@realworldtech.com>
Subject: Re: Why I can't use `info' in emacs?
Date: 20 Dec 2006 08:51:57 -0800	[thread overview]
Message-ID: <1166633517.106935.22620@f1g2000cwa.googlegroups.com> (raw)
In-Reply-To: <878xh3nzda.fsf@kobe.laptop>

Giorgos Keramidas wrote:
> On 18 Dec 2006 03:51:43 -0800,
> "Robert Thorpe" <rthorpe@realworldtech.com> wrote:
> >Giorgos Keramidas wrote:
> >>On 15 Dec 2006 06:57:13 -0800,
> >>"Robert Thorpe" <rthorpe@realworldtech.com> wrote:
> >>>> ,----
> >>>> | PRINTF(3)    Linux Programmer's Manual    <snip>
> >>>>
> >>>> Surely the man pages are superior in this instance for a programmer?
> >>>
> >>> It depends.  [...]
> >>> The man-page is quite thorough in this case, but it is a little
> >>> confusing in one respect, It says "Linux Programmer's Manual".  I
> >>> have no idea why it says this, since printf is provided by Glibc.
> >>
> >> That's because man pages are organized in sections.  The section title
> >> for manpages in section 3 is "Linux Programmer's Manual" on Linux.  On
> >> other systems, section 3 may have a slightly different title.  Here, for
> >> instance, on a FreeBSD system, the title is:
> >>
> >> PRINTF(3)             FreeBSD Library Functions Manual            PRINTF(3)
> >
> > I don't agree.  Individual man pages should have titles, not just
> > sections of the manual.
>
> I think there may have been a moderate amount of confusion here.  I thought
> you didn't know why the header says "Linux Programmer's Manual", not that
> you knew all about manpage sections but you disagreed with the content of
> the text.

Fair point.

> The most commonly used packages for writing manpages are "man" and "mandoc"
> these days.  They both provide ways to set the manpage header to a
> package-specific string, so if you don't like the Glibc manpage headers,
> then maybe it's a good idea to contact teh Glibc authors :)

Glibc doesn't contain man-pages.  The man pages were written mainly by
the people who document the linux kernel, that's why it says "Linux
Programmer's Manual".  This is an overhang from the days when Linux
used Libc6 which was maintained by Linux kernel folks.  It's confusing
because they don't maintain that part of the system anymore.

> Yep.  Agreed 100%.
>
> > The FreeBSD entry is entirely correct, since FreeBSD's libc is
> > maintained with FreeBSD.
>
> Since it is up to the manpage author to set the header to something like
> "GNU C Library Functions Manual", or even "SDL API Reference", even in
> FreeBSD some manpages have the 'wrong' header, by your criteria :-/

Yep.  It's a fairly common problem, not restricted to manpages either.

  reply	other threads:[~2006-12-20 16:51 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-14 23:59 Why I can't use `info' in emacs? Ronald
2006-12-15  6:50 ` Harald Hanche-Olsen
2006-12-15  7:15   ` Ronald
2006-12-15 12:40     ` Robert Thorpe
2006-12-15 14:18       ` Eli Zaretskii
2006-12-15  8:39 ` Eli Zaretskii
     [not found] ` <mailman.1908.1166172009.2155.help-gnu-emacs@gnu.org>
2006-12-15  9:20   ` Ronald
2006-12-15 11:17     ` Eli Zaretskii
     [not found]     ` <mailman.1911.1166181447.2155.help-gnu-emacs@gnu.org>
2006-12-15 13:49       ` Hadron Quark
2006-12-15 14:02         ` Robert Thorpe
2006-12-15 14:13           ` Hadron Quark
2006-12-15 14:25           ` Hadron Quark
2006-12-15 14:57             ` Robert Thorpe
2006-12-15 15:49               ` Hadron Quark
2006-12-15 17:41                 ` Robert Thorpe
2006-12-18  0:10               ` Giorgos Keramidas
2006-12-18 11:51                 ` Robert Thorpe
2006-12-20  1:13                   ` Giorgos Keramidas
2006-12-20 16:51                     ` Robert Thorpe [this message]
2006-12-15 15:57             ` Eli Zaretskii
     [not found]             ` <mailman.1922.1166198262.2155.help-gnu-emacs@gnu.org>
2006-12-15 16:27               ` Hadron Quark
2006-12-15 18:11                 ` Robert Thorpe
2006-12-16 19:21                   ` Hadron Quark
2006-12-16 21:51                     ` Eli Zaretskii
     [not found]                     ` <mailman.1996.1166305877.2155.help-gnu-emacs@gnu.org>
2006-12-16 22:30                       ` Hadron Quark
2006-12-17  4:12                         ` Eli Zaretskii
     [not found]                         ` <mailman.2006.1166328762.2155.help-gnu-emacs@gnu.org>
2006-12-18 12:54                           ` Hadron Quark
2006-12-18 20:01                             ` Eli Zaretskii
2006-12-18 10:44                     ` Robert Thorpe
2006-12-18 12:56                       ` Hadron Quark
2006-12-18 13:12                         ` Robert Thorpe
2006-12-18 17:11                           ` Hadron Quark
2006-12-18 17:27                             ` Robert Thorpe
2006-12-16 12:04                 ` Eli Zaretskii
2006-12-15  9:20   ` Ronald

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1166633517.106935.22620@f1g2000cwa.googlegroups.com \
    --to=rthorpe@realworldtech.com \
    /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.
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 read-only IMAP folder(s) and NNTP newsgroup(s).