From: Hadron Quark <hadronquark@gmail.com>
Subject: Re: Why I can't use `info' in emacs?
Date: Mon, 18 Dec 2006 13:54:54 +0100 [thread overview]
Message-ID: <afhcvtbbz5.fsf@gmail.com> (raw)
In-Reply-To: mailman.2006.1166328762.2155.help-gnu-emacs@gnu.org
Eli Zaretskii <eliz@gnu.org> writes:
>> From: Hadron Quark <hadronquark@gmail.com>
>> Date: Sat, 16 Dec 2006 23:30:08 +0100
>>
>> Again : Did you *read* the excerpts I posted coming up from the code? As a first
>> page context help, the man page is superior to the info file node which
>> first appears. From a programming perspective. Here it is again :
>
> Instead of insisting that the superiority is obvious, why don't you
> tell what you, from your programming perspective, expect to find when
> you ask the help system about a function? Then, if that information
> is missing from the glibc manual, perhaps some day it will be added.
>
> If you keep insisting that it's obvious, one thing is certain: the
> manual will never be changed to your liking. Maybe that is your
> goal...
I would have thought that me stating I wanted context help from the code
would make it obvious if you look at the two excerpts.
One gives the function API and the overview, the other doesnt.
next prev parent reply other threads:[~2006-12-18 12:54 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
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 [this message]
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=afhcvtbbz5.fsf@gmail.com \
--to=hadronquark@gmail.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).