unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Jay Belanger <jay.p.belanger@gmail.com>
To: Personal <gokul_ps@yahoo.com>
Cc: 16750@debbugs.gnu.org
Subject: bug#16750: Feedback on the manual
Date: Sun, 16 Feb 2014 20:58:26 -0600	[thread overview]
Message-ID: <87d2im5tt9.fsf@gmail.com> (raw)
In-Reply-To: <20140217015420.5533840.47014.903@yahoo.com> (Personal's message of "Mon, 17 Feb 2014 07:24:20 +0530")


> I still can't think of a scenario where one would want to keep
> jumping.

...

> And yes, you can't satisfy everyone. You need not, as well.. But still
> there should be people who might feel the same way as me..

People like you don't need to jump; nobody is forced to.

> and as long as you care.. one quick suggestion would be to release a
> short user guide (different from manual) with enough pictures and no
> hyperlinks which will help people quickly to begin with, and later
> proceed with the manual in place..

Eli pointed out that pictures is a good idea.  Does the tutorial count
as a short user guide?  What about the guided tour?  Actually, the
guided tour has a lot of pictures included in it.
Since nobody is forced to use hyperlinks, there is no reason for them to
be omitted.  People who don't want them can ignore them, people who want
them can follow them.

> Regarding the 'C-h t' part.. yes the YouTube video taught me where and
> how I need to issue that command..

The Emacs Help menu also takes you to the tutorial, which tells you what
the commands do.

> I don't want this to be an argument on who's right.. but as long as
> you're ready to lend ears to some suggestions, I would once again like
> to quote the picture thing.. window, buffer or whatever terminology
> you try to explain there with alphanumeric, try with a picture
> instead. That will serve the purpose..

More pictures might be useful; currently, the Guided tour is heavily
illustrated. 

> Once again.. I really really appreciate your efforts.. though I have
> some concerns, you have did a great job there and I appreciate it..
> regarding volunteering, not sure how long it takes for me to master
> emacs, but when I do.. I would definitely contribute in ways I can..

You don't need to master Emacs to contribute; in fact, if you are trying
to help with the beginning information, suggestions from someone not
familiar with Emacs might be the most helpful.  

When Emacs starts up (unless the splash screen is turned off), there is
a list of resources for learning Emacs.  Is there anything else you
think should be there?  I would think the tutorial would be where new
users would start off.  I take it you think the tutorial should contain
images; any other suggestions?






  reply	other threads:[~2014-02-17  2:58 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
2014-02-17  1:54           ` Personal
2014-02-17  2:58             ` Jay Belanger [this message]
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

  List information: https://www.gnu.org/software/emacs/

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

  git send-email \
    --in-reply-to=87d2im5tt9.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 public inbox

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

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