From: Ricardo Wurmus <rekado@elephly.net>
To: Mark H Weaver <mhw@netris.org>
Cc: "help-guix@gnu.org" <help-guix@gnu.org>
Subject: Re: Manual pages for glibc.
Date: Sat, 12 Aug 2017 23:09:58 +0200 [thread overview]
Message-ID: <87lgmoh4rd.fsf@elephly.net> (raw)
In-Reply-To: <87o9rkmrde.fsf@netris.org>
Mark H Weaver <mhw@netris.org> writes:
> Hi Ricardo,
>
> Ricardo Wurmus <rekado@elephly.net> writes:
>
>>> Which package do I need to install to be able to read the man pages of
>>> functions in glibc like 'snprintf' and 'malloc'?
>>>
>>> I installed glibc, but that does not seem to provide the man pages.
>>
>> Here’s what I did:
>>
>> unionfs $(printf "%s:" /gnu/store/*/share/info) ~/tmp/info
>>
>> This gives me a union of all the beautiful info manuals in the store.
>> To read the GNU libc’s info manual I do this in Emacs:
>>
>> C-u C-h i ~/tmp/info/libc.info.gz RET
>
> This awkward solution should not be needed. I simply installed
> 'gcc-toolchain' in my user profile and access the info manuals in Emacs
> using C-h i. Does that not work for you?
It’s not a solution in response to wanting to access libc; I did this
because I wanted to have access to all info manuals, regardless of
whether I have the packages in my profile or not. I just like browsing
them.
--
Ricardo
GPG: BCA6 89B6 3655 3801 C3C6 2150 197A 5888 235F ACAC
https://elephly.net
next prev parent reply other threads:[~2017-08-12 21:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-09 8:49 Manual pages for glibc Roel Janssen
2017-08-09 11:18 ` Ricardo Wurmus
2017-08-09 11:49 ` Roel Janssen
2017-08-12 21:02 ` Mark H Weaver
2017-08-12 21:09 ` Ricardo Wurmus [this message]
2017-08-09 19:43 ` Alex Kost
2017-08-09 20:23 ` Roel Janssen
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://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87lgmoh4rd.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=help-guix@gnu.org \
--cc=mhw@netris.org \
/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).