unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Hadron Quark <hadronquark@gmail.com>
Subject: Re: Why I can't use `info' in emacs?
Date: Sat, 16 Dec 2006 20:21:32 +0100	[thread overview]
Message-ID: <jwwt4ry7cz.fsf@gmail.com> (raw)
In-Reply-To: 1166206305.278573.25520@n67g2000cwd.googlegroups.com

"Robert Thorpe" <rthorpe@realworldtech.com> writes:

> Hadron Quark wrote:
>> Eli Zaretskii <eliz@gnu.org> writes:
>>
>> >> From: Hadron Quark <hadronquark@gmail.com>
>> >> Date: Fri, 15 Dec 2006 15:25:55 +0100
>> >>
>> >> Surely the man pages are superior in this instance for a programmer?
>> >
>> > How is the man page superior?
>> >
>>
>> Did you look at the excerpts which came up from the context. For a
>> programmer bringing up the API it is blatantly obvious, in this case,
>> which first stage info is more useful.
>
> The most common reason I have for looking at API docs is to remind me
> of the order of arguments in a function.  Mostly I can remember the
> functions purpose.  We're all different.
>

Hence the man page is superior :-;

-- 

  reply	other threads:[~2006-12-16 19:21 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 [this message]
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=jwwt4ry7cz.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).