unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Catonano <catonano@gmail.com>
To: "Clément Lassieur" <clement@lassieur.org>
Cc: help-guix <help-guix@gnu.org>
Subject: Re: invoking info guix
Date: Sat, 17 Mar 2018 11:18:33 +0100	[thread overview]
Message-ID: <CAJ98PDzxgEcndMoqS7D_zAxReSt0JZvCZ-MBcL2kf7R02QSb_w@mail.gmail.com> (raw)
In-Reply-To: <87k1ubf20m.fsf@lassieur.org>

[-- Attachment #1: Type: text/plain, Size: 1578 bytes --]

2018-03-17 11:08 GMT+01:00 Clément Lassieur <clement@lassieur.org>:

> Catonano <catonano@gmail.com> writes:
>
> > In a terminal I can issue this command
> >
> > ~$ info guix
> >
> > and have the guuix manual pop up
> >
> > In Emacs I can do
> >
> > M-x info
> >
> > but then I find myself in a general page, a sort of index and I have to
> > search through it in order to find the guix "link"
> >
> > How can I end up in the Guix manual front page directly even when using
> > Emacs ?
> >
> > Thanks
>
> Hi Catonano,
>
> As Arun and Oleg said, 'm' is very useful (maybe with C-u), and 'd'
> too.  And there is the 'info-display-manual' command too.
>

I tried m right now and it suffices

helm is awesome but I don' t want to install further packages and learn new
things.
I just want to be ushered in the Guix info page right....  now ;-)


> 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 ;-)

Now, now, I'm perfectly aware of the historical and cultural differences ;-)

I was a young adult back then and changing habits is harder and harder with
the flow of the time

I' ll take a look at the info info page though

You gotta give me I came a loooong way !! :-)

Thank you all people for your suggestions !
Ciao

[-- Attachment #2: Type: text/html, Size: 2547 bytes --]

  reply	other threads:[~2018-03-17 10:18 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 [this message]
2018-03-17 12:20     ` Oleg Pykhalov

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=CAJ98PDzxgEcndMoqS7D_zAxReSt0JZvCZ-MBcL2kf7R02QSb_w@mail.gmail.com \
    --to=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).