From: Gokul Kannan <gokul_ps@yahoo.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: "16750@debbugs.gnu.org" <16750@debbugs.gnu.org>
Subject: bug#16750: Feedback on the manual
Date: Sat, 15 Feb 2014 23:38:20 -0800 (PST) [thread overview]
Message-ID: <1392536300.55209.YahooMailNeo@web125006.mail.ne1.yahoo.com> (raw)
In-Reply-To: <8361ohdbnu.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1643 bytes --]
Did you try not to follow them? They are only there for those who
want the details.
//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..
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..
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..
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..
Thanks,
Gokul
________________________________
From: Eli Zaretskii <eliz@gnu.org>
To: Gokul Kannan <gokul_ps@yahoo.com>
Cc: 16750@debbugs.gnu.org
Sent: Friday, 14 February 2014 7:44 PM
Subject: Re: bug#16750: Feedback on the manual
> Date: Fri, 14 Feb 2014 03:59:57 -0800 (PST)
> From: Gokul Kannan <gokul_ps@yahoo.com>
> Cc: "16750@debbugs.gnu.org" <16750@debbugs.gnu.org>
>
> One quick thing anyone could notice is.. You guys have tried to explain the various components of emac without a pic.. A big fail..
Yes, I guess pictures will be worth about a thousand words.
Volunteers are welcome.
> And the other thing i already pointed.. wasn't that specific.? Endless hyperlinks pointing to further pages makes the guide clumsy and spoils the reading experience.
Did you try not to follow them? They are only there for those who
want the details.
[-- Attachment #2: Type: text/html, Size: 5621 bytes --]
next prev parent reply other threads:[~2014-02-16 7:38 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 [this message]
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
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=1392536300.55209.YahooMailNeo@web125006.mail.ne1.yahoo.com \
--to=gokul_ps@yahoo.com \
--cc=16750@debbugs.gnu.org \
--cc=eliz@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.
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).