From: Oleg Pykhalov <go.wigust@gmail.com>
To: Catonano <catonano@gmail.com>
Cc: help-guix <help-guix@gnu.org>, "Clément Lassieur" <clement@lassieur.org>
Subject: Re: invoking info guix
Date: Sat, 17 Mar 2018 15:20:43 +0300 [thread overview]
Message-ID: <87k1uarizo.fsf@gmail.com> (raw)
In-Reply-To: <CAJ98PDzxgEcndMoqS7D_zAxReSt0JZvCZ-MBcL2kf7R02QSb_w@mail.gmail.com> (catonano@gmail.com's message of "Sat, 17 Mar 2018 11:18:33 +0100")
[-- Attachment #1: Type: text/plain, Size: 925 bytes --]
Catonano <catonano@gmail.com> writes:
> 2018-03-17 11:08 GMT+01:00 Clément Lassieur <clement@lassieur.org>:
[…]
>> But what you should really do (in my humble opinion :-)) is to read the
>> (info "info") manual. It is very well done and explains everything in
>> an interactive way.
>>
>
> I have a reading phobia :-)
>
> My first computer as an adult was an Apple Macintosh
>
> At the time the mantra was that if something required a manual to be read,
> it was not well made ;-)
First of all GNU Documentation is not Apple manual. :-)
You don't need to read it at once and remember, because you have it
always at your finger tips with handful feautures to search for
something really fast. The only feauture (which I found useful for ‘M-x
occur’) not described in the "(info)" manual is that you could ‘M-x
widen’ or ‘<C-x n w>’ and look on info page all at once.
Oleg.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
prev parent reply other threads:[~2018-03-17 12:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-17 6:54 invoking info guix Catonano
2018-03-17 8:38 ` Nicolas Goaziou
2018-03-17 8:57 ` Oleg Pykhalov
2018-03-17 9:51 ` Arun Isaac
2018-03-17 10:08 ` Clément Lassieur
2018-03-17 10:18 ` Catonano
2018-03-17 12:20 ` Oleg Pykhalov [this message]
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=87k1uarizo.fsf@gmail.com \
--to=go.wigust@gmail.com \
--cc=catonano@gmail.com \
--cc=clement@lassieur.org \
--cc=help-guix@gnu.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).