From: Eli Zaretskii <eliz@gnu.org>
To: vaidheeswaran.chinnaraju@gmail.com
Cc: emacs-devel@gnu.org
Subject: Re: What would an "An Official" GNU Emacs Book look like?
Date: Sun, 10 May 2015 17:40:14 +0300 [thread overview]
Message-ID: <83a8xco5rl.fsf@gnu.org> (raw)
In-Reply-To: <mimtju$e03$1@ger.gmane.org>
> From: Vaidheeswaran C <vaidheeswaran.chinnaraju@gmail.com>
> Date: Sun, 10 May 2015 11:55:52 +0530
>
> On Saturday 09 May 2015 04:09 PM, Eli Zaretskii wrote:
> >> From: Vaidheeswaran C <vaidheeswaran.chinnaraju@gmail.com>
> >> Date: Sat, 09 May 2015 14:59:04 +0530
> >>
> >> I have never read a Emacs Book myself (and I have no idea how they are
> >> typically structured). I learnt Emacs using the tutorial. These days
> >> Info is my friend.
> >
> > That "Info" _is_ the Emacs book we have.
>
> The one that is in the FSF shop,
>
> 1. Is it just ./doc/emacs/emacs.pdf?
Basically. There's also the Emacs Lisp manual.
> 2. Does it include other Info manuals? If yes, what are these?
See above.
But all that might be outdated knowledge, you were already advised by
Richard to check out what the FSF sells these days.
next prev parent reply other threads:[~2015-05-10 14:40 UTC|newest]
Thread overview: 79+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-08 5:52 What would an "An Official" GNU Emacs Book look like? Vaidheeswaran C
2015-05-08 7:49 ` Eli Zaretskii
2015-05-08 15:03 ` Stefan Monnier
2015-05-08 17:08 ` Vaidheeswaran C
2015-05-08 22:16 ` Stefan Monnier
2015-05-09 9:29 ` Vaidheeswaran C
2015-05-09 10:39 ` Eli Zaretskii
2015-05-10 6:25 ` Vaidheeswaran C
2015-05-10 14:40 ` Eli Zaretskii [this message]
2015-05-10 15:26 ` Richard Stallman
2015-05-17 15:54 ` Vaidheeswaran C
2015-05-17 17:22 ` Emanuel Berg
2015-05-17 21:55 ` Richard Stallman
2015-05-17 23:23 ` Emanuel Berg
2015-05-18 2:37 ` Vaidheeswaran C
2015-05-18 2:21 ` Vaidheeswaran C
2015-05-18 2:41 ` Emanuel Berg
2015-05-18 2:50 ` Stephen J. Turnbull
2015-05-18 3:00 ` Vaidheeswaran C
2015-05-18 4:01 ` Stephen J. Turnbull
2015-05-18 4:41 ` Vaidheeswaran C
2015-05-18 14:17 ` Eli Zaretskii
2015-05-18 18:11 ` Timur Aydin
2015-05-20 5:50 ` Stephen J. Turnbull
2015-05-18 19:14 ` Marcin Borkowski
2015-05-18 20:15 ` Emanuel Berg
2015-05-19 11:05 ` Richard Stallman
2015-05-19 23:12 ` Emanuel Berg
2015-05-20 13:33 ` Richard Stallman
2015-05-20 13:33 ` Richard Stallman
2015-05-21 3:20 ` Stephen J. Turnbull
2015-05-21 4:18 ` Vaidheeswaran C
2015-05-21 11:33 ` Richard Stallman
2015-05-21 18:53 ` chad
2015-05-22 21:31 ` Richard Stallman
2015-05-24 21:20 ` chad
2015-05-24 22:56 ` Emanuel Berg
2015-05-25 15:29 ` Richard Stallman
2015-05-25 18:05 ` chad
2015-05-26 11:54 ` Richard Stallman
2015-05-26 18:02 ` chad
2015-05-27 14:25 ` Richard Stallman
2015-05-28 5:15 ` chad
2015-05-28 12:31 ` Richard Stallman
2015-05-28 17:47 ` chad
2015-05-30 2:44 ` Mark H Weaver
2015-05-30 20:16 ` chad
2015-05-31 14:04 ` Richard Stallman
2015-05-21 19:39 ` Stephen J. Turnbull
2015-05-21 11:33 ` Richard Stallman
2015-05-21 19:45 ` Stephen J. Turnbull
2015-05-22 21:32 ` Richard Stallman
2015-05-23 3:33 ` Stephen J. Turnbull
2015-05-21 23:29 ` Emanuel Berg
2015-05-30 4:42 ` Vaidheeswaran C
2015-05-30 12:18 ` Rasmus
2015-05-19 6:12 ` Vaidheeswaran C
2015-05-20 5:50 ` Stephen J. Turnbull
2015-05-18 6:04 ` David Engster
2015-05-18 16:23 ` Stefan Monnier
2015-05-18 18:54 ` Richard Stallman
2015-05-19 4:34 ` Vaidheeswaran C
2015-05-18 16:53 ` Filipp Gunbin
2015-05-18 16:55 ` Filipp Gunbin
2015-05-19 5:12 ` Vaidheeswaran C
2015-05-08 22:12 ` chad
2015-05-09 14:16 ` Richard Stallman
2015-05-09 16:03 ` Marcin Borkowski
2015-05-10 15:27 ` Richard Stallman
2015-05-18 20:15 ` Marcin Borkowski
2015-05-18 21:15 ` Emanuel Berg
2015-05-19 1:16 ` Emanuel Berg
2015-05-19 11:05 ` Richard Stallman
2015-05-19 18:56 ` Marcin Borkowski
2015-05-19 19:44 ` Richard Stallman
2015-05-19 20:06 ` Alan Mackenzie
2015-05-19 20:33 ` Marcin Borkowski
2015-05-20 13:31 ` Richard Stallman
2015-05-08 18:46 ` Richard Stallman
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=83a8xco5rl.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=vaidheeswaran.chinnaraju@gmail.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.