all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Jay Belanger <jay.p.belanger@gmail.com>
To: Gokul Kannan <gokul_ps@yahoo.com>
Cc: "16750@debbugs.gnu.org" <16750@debbugs.gnu.org>
Subject: bug#16750: Feedback on the manual
Date: Sun, 16 Feb 2014 15:14:24 -0600	[thread overview]
Message-ID: <87lhxa69qn.fsf@gmail.com> (raw)
In-Reply-To: <1392536300.55209.YahooMailNeo@web125006.mail.ne1.yahoo.com> (Gokul Kannan's message of "Sat, 15 Feb 2014 23:38:20 -0800 (PST)")


> //I tried not to follow the endless hyperlinks, but it just spoils the
> reading experience.
>
> Who would want to jump to advanced, when you have not even explained
> the basics yet..

I might, in some situations.  Others might not.  It's good to offer the
choice.

> Majority of people wouldn't be interested to read like this.. read
> page number 10 -- then jump to 200.. then come back to 11.. go till
> 20.. then jump to 989.. 

The majority of people wouldn't need to.  The links are for those that
want the extra information.  The choices seem to be:
  * Put all of the information up front.
    This could be offputting for those that don't want the advanced 
    information right away.
  * Don't let the users know where to get more advanced information.
    Why keep it a secret?
  * Provide the basic information, and link to more information for
    those who want it.
    It seems like a good choice to me, but you can't please everyone. 

> If you feel the details at 989 is very much needed to what you have
> explained at 20, then it should be page number 21 and not 989..

And if you think that the details at 989 aren't very much needed, but
want to let people who might be interested know where to get it right
away, a link sounds like a good idea.

> Finally, I would like to get my hands on emacs.. But couldn't find a
> proper guide yet.. Guide me with some hyperlinks/articles on emacs for
> beginners that you're aware of..

When you start Emacs, you are given a message:
   "For information about GNU Emacs and the GNU system, type C-h C-a."
Typing C-hC-a leads you to hyperlinks/articles on using Emacs (and other
information, too).  It's possible that someone doesn't know what
"C-hC-a" means (it's explained in the tutorial), but there is a Help
menu, whose first menu item is the Emacs tutorial.





  parent reply	other threads:[~2014-02-16 21:14 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-14  7:00 bug#16750: Feedback on the manual Gokul Kannan
2014-02-14  7:42 ` Eli Zaretskii
2014-02-14 11:59   ` Gokul Kannan
2014-02-14 14:14     ` Eli Zaretskii
2014-02-16  7:38       ` Gokul Kannan
2014-02-16 19:45         ` Bastien
2014-02-16 21:14         ` Jay Belanger [this message]
2014-02-17  1:54           ` Personal
2014-02-17  2:58             ` Jay Belanger
2014-02-17  3:11               ` Personal
2019-09-26 17:06                 ` Lars Ingebrigtsen

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87lhxa69qn.fsf@gmail.com \
    --to=jay.p.belanger@gmail.com \
    --cc=16750@debbugs.gnu.org \
    --cc=gokul_ps@yahoo.com \
    /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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.