From: David Hansen <david.hansen@gmx.net>
Subject: Re: Jump to man page buffer
Date: Tue, 12 Sep 2006 19:17:57 +0200 [thread overview]
Message-ID: <87slix6m2i.fsf@robotron.kosmorama> (raw)
In-Reply-To: 87zmd6xare.fsf@gmail.com
On Tue, 12 Sep 2006 01:07:49 +0200 Hadron Quark wrote:
> robert.thorpe@antenova.com writes:
>
>> Hadron Quark wrote:
>>> I have the following code mapped to f1.
>>>
>>> "manual-entry (current-word)"
>>>
>>> How to make emacs also jump to the buffer showing the resulting
>>> man-page?
>>>
>>> thanks for any help.
>>
>> As a side-note, using man pages as references is trouble in systems
>> that use GNU components heavily.
>>
>> The best docs of most of the general utilities are the info pages, the
>> best docs to glibc are generally the info pages. The best/only docs to
>> the kernel stuff and system utilities are the man pages.
>>
>
> Didnt know that.
>
> I tried "info(current-word)" but it doesnt work.
>
> How would I bring up the info for C functions then? Ideally use the info
> page if it exists or else revert to the man page.
Install the GNU libc info manual and use it like you use the
other info manuals.
Anyway i disagree with Robert. I would think that on every
POSIX box it's more likely that the manual pages are available
than the libc info manual.
And for a quick lookup the manual pages are usually better.
In contrast the libc manual is a bit more descriptive and
comes with more examples. Both have it's use.
David
next prev parent reply other threads:[~2006-09-12 17:17 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-09 20:49 Jump to man page buffer Hadron Quark
2006-09-09 21:34 ` Thorsten Bonow
2006-09-09 22:35 ` Hadron Quark
2006-09-09 22:50 ` Thorsten Bonow
2006-09-09 23:07 ` Hadron Quark
2006-09-09 23:13 ` Thorsten Bonow
2006-09-10 20:08 ` David Hansen
2006-09-11 15:26 ` Kevin Rodgers
2006-09-11 15:42 ` robert.thorpe
2006-09-11 23:07 ` Hadron Quark
2006-09-12 17:17 ` David Hansen [this message]
2006-09-12 17:54 ` robert.thorpe
2006-09-12 19:27 ` David Hansen
2006-09-12 19:51 ` Drew Adams
2006-09-12 21:46 ` David Hansen
2006-09-12 22:00 ` Drew Adams
[not found] ` <mailman.6840.1158098039.9609.help-gnu-emacs@gnu.org>
2006-09-13 9:40 ` robert.thorpe
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=87slix6m2i.fsf@robotron.kosmorama \
--to=david.hansen@gmx.net \
/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).