From: Elena <egarrulo@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: Re: Do we need a "Stevens" book?
Date: Thu, 29 Jul 2010 03:02:32 -0700 (PDT) [thread overview]
Message-ID: <093d461d-5402-4226-80d5-6e3d8df2b922@j8g2000yqd.googlegroups.com> (raw)
In-Reply-To: mailman.0.1280385826.20966.help-gnu-emacs@gnu.org
On Jul 29, 6:40 am, Thien-Thi Nguyen <t...@gnuvola.org> wrote:
> Why does the search start with Google (and continue with other
> downstream, non-terminating, whirlpool-shaped, out of date, referenda)?
> Why not go to the source? The Emacs Lisp manual, the Emacs Lisp code,
> the Emacs customization facility, the Emacs *scratch* buffer, the Emacs!
Surprisingly enough - or not? - it seems few users do read the
manuals... I'm guilty of this too (and Emacs' manuals will be my
reading on my next vacations). Emacs is too much a complex (not
difficult) and powerful software to be used by intuition alone, unlike
many softwares we are used to.
RTFM! RTFM! RTFM! ...
next prev parent reply other threads:[~2010-07-29 10:02 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-28 16:42 Do we need a "Stevens" book? Olwe Melwasul
2010-07-28 17:47 ` Andreas Röhler
2010-07-28 17:48 ` Richard Riley
2010-07-29 6:40 ` Thien-Thi Nguyen
2010-07-30 12:28 ` Thien-Thi Nguyen
2010-07-31 4:47 ` Ken Hori
[not found] ` <mailman.0.1280385826.20966.help-gnu-emacs@gnu.org>
2010-07-29 9:50 ` rustom
2010-07-29 10:02 ` Elena [this message]
[not found] ` <35282104-5b51-4ba4-8745-4fae239ce0ee@q21g2000prm.googlegroups.com>
2010-07-30 5:29 ` Fren Zeee
2010-07-31 5:47 ` have you read emacs manual cover to cover?; (was Do we need a "Stevens" book?) Xah Lee
[not found] ` <63e9cab8-17da-4f1a-b055-e172a3ffeb47@o7g2000prg.googlegroups.com>
2010-08-08 12:02 ` Xah Lee
[not found] <mailman.1.1280335348.2485.help-gnu-emacs@gnu.org>
2010-07-28 17:01 ` Do we need a "Stevens" book? Pascal J. Bourguignon
2010-07-28 23:15 ` Stefan Monnier
2010-08-01 17:07 ` Joseph Brenner
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=093d461d-5402-4226-80d5-6e3d8df2b922@j8g2000yqd.googlegroups.com \
--to=egarrulo@gmail.com \
--cc=help-gnu-emacs@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 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.