unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: myglc2 <myglc2@gmail.com>
To: Fox <firefox@firemail.cc>
Cc: help-guix@gnu.org
Subject: Re: Emacs-Guix 0.3.1
Date: Mon, 22 May 2017 22:48:56 -0400	[thread overview]
Message-ID: <86efvgb84n.fsf@gmail.com> (raw)
In-Reply-To: <ofu00f$hqk$1@blaine.gmane.org> (Fox's message of "Mon, 22 May 2017 08:21:09 +0200")

On 05/22/2017 at 08:21 Fox writes:

>  Alex Kost wrote:
>
>> if you don't like to read "info", Emacs-Guix manual is available
>> online now:
>
>  https://alezost.github.io/guix.el/manual/latest/html_node/index.html
>
>
> html sure is better workable than the "info" format.
>
> But then, some GNU documentation suffers from lack of ability to
> explain things to folks who do NOT know it all already.
>
> case in point:
> https://www.gnu.org/software/emacs/manual/html_mono/eshell.html#Invocation
>
>
> if you expected to be told how to invoke an eshell, forget it.
> That whole manual is only useful if you ALREADY know that you need to
> press ALT-x eshell RETURN and the menus (where in a real editor such a
> function would be available) will let you down, so don't even bother
> to search eamcs menus for "eshell". So instead of reading the GNU
> manual on eshell you better do what you always do: google it and often
> times succeed.


Actually, 'google it' failed you here: The top 'google eshell' didn't
answer you question.

If you had run emacs, typed 'M-x info m emacs C-s eshell C-s' you would
have read ...

   ‘M-x eshell’ invokes a shell implemented entirely in Emacs.  It is
documented in its own manual.  *Note Eshell: (eshell)Top.


google/HTML is worse than emacs/INFO for a number of reasons. One of
them: Google typically shows you the DOC for a different software
version than you are trying to use. So you end up wasting many hours
reading all about how the software you are running does NOT work and
wondering what on earth is wrong. If you will invest an hour learning
how to use emacs/INFO you will save many such hours ;-)


Agreed, the top 'google eshell' hit could be improved. If you 'google
eshell bugs' it takes you to ...

https://www.gnu.org/software/emacs/manual/html_node/eshell/Bugs-and-ideas.html

If, as it suggests, you run emacs type 'M-x report-emacs-bug' and attach
your original email, it might even be ;-)

      parent reply	other threads:[~2017-05-23  2:49 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-05 19:00 [ANN] Emacs-Guix 0.3.1 Alex Kost
2017-05-22  6:21 ` Fox
2017-05-22  8:51   ` Clément Lassieur
2017-05-22 17:25   ` Ricardo Wurmus
2017-05-24 11:56     ` Ludovic Courtès
2017-05-23  2:48   ` myglc2 [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=86efvgb84n.fsf@gmail.com \
    --to=myglc2@gmail.com \
    --cc=firefox@firemail.cc \
    --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).