all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: florian@fsavigny.de (Florian v. Savigny)
To: help-gnu-emacs@gnu.org
Subject: Re: Emacs and Lynx Browser
Date: Fri, 24 May 2013 18:40:07 -0400	[thread overview]
Message-ID: <E1Ug0ec-0000N2-1Y@eggs.gnu.org> (raw)
In-Reply-To: <87r4gwkvmo.fsf@VLAN-3434.student.uu.se> (message from Emanuel Berg on Fri, 24 May 2013 21:47:43 +0200)



  > Pascal c <pch.netz@gmail.com> writes:
  > 
  > > I'm starting to learn Emacs. It's not easy but I can already
  > > feel how intresting it is.

Good instinct. ;-) (No - I mean it.)

  > There are some great books for you to pick up. I read the 1988 manual
  > by Richard Stallman and also a modern book called "Learning GNU
  > Emacs". 

You probably mean the green-white one published by O'Reilly? (By Debra
Whatshername, and a guy - maybe even Eric Raymond, originally?). That
was the one that got me hooked back in about 1998, so I would also
recommend it (a factor to consider, however, might be how new the
latest edition is. But then, even an outdated one might help a
lot.). Since then, Emacs has been the centre of practically everything
for me.

  > In many general-purpose GNU/Linux introductions, there are
  > chapters on Emacs, but those typically only cover what you already
  > know: cursor movements, filling paragraphs, splitting windows... That's
  > why getting "Emacs only" books is something I benefited from, a lot.

Interestingly, there are comparatively few Emacs books around, which
is surprising given the stellar respectability the program has earned,
and its versatility. (Compare that to the number of Perl books around
- it's striking, isn't it? I once took Damian Conway's "Perl Best
Practices" and started to apply them to Elisp, because much was
transferable.)

The nice thing about the O'Reilly book is that it does a modest amount
of advertising Emacs. I still remember one thing they kept mentioning:
That it was integration that made Emacs so interesting. This is still
true fifteen years later. The manual, as far as I know it, is
"dryer". Nevertheless, I would say it is also worth reading in
print. If you like to program, the Introduction into Emacs Lisp by
Robert Cha... (forgotten the rest) is also not bad.

Later, you discover so much well-done self-documentation and
-demonstration (C-h f, C-h F, C-h C-h, C-x C-e, C-j in the *scratch*
buffer, and edebug-defun) that reading becomes increasingly
unnecessary.

(Sorry if that was trivial for most. I just could not resist relating
the essence of my own experience. Over the years, Emacs has helped me
enormously in two very different jobs - translator and teacher -, and
that was because I could always tweak it to do what I wanted. It
allows you to do those simple things that you normally only imagine.)

Best, 

Florian




  reply	other threads:[~2013-05-24 22:40 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.25829.1368604292.855.help-gnu-emacs@gnu.org>
2013-05-15 14:37 ` Emacs and Lynx Browser Emanuel Berg
2013-05-16 12:34   ` Pascal c
2013-05-16 12:41     ` Mark Skilbeck
2013-05-16 12:54     ` Suvayu Ali
2013-05-17  9:35       ` Jude DaShiell
2013-05-24  6:42         ` Pascal c
     [not found]         ` <mailman.298.1369377779.22516.help-gnu-emacs@gnu.org>
2013-05-24 19:47           ` Emanuel Berg
2013-05-24 22:40             ` Florian v. Savigny [this message]
     [not found]             ` <mailman.343.1369435210.22516.help-gnu-emacs@gnu.org>
2013-05-24 23:00               ` Emanuel Berg
2013-05-25  7:21                 ` Emacs books (was: Emacs and Lynx Browser) Florian v. Savigny
     [not found]                 ` <mailman.361.1369466476.22516.help-gnu-emacs@gnu.org>
2013-05-25  9:32                   ` Emanuel Berg
     [not found]   ` <mailman.25904.1368707682.855.help-gnu-emacs@gnu.org>
2013-05-16 13:53     ` Emacs and Lynx Browser Emanuel Berg
2013-05-15  7:51 Pascal c
2013-05-15  8:46 ` Peter Dyballa
2013-05-15  9:11 ` Jonathan Groll

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=E1Ug0ec-0000N2-1Y@eggs.gnu.org \
    --to=florian@fsavigny.de \
    --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.