From: Tim X <timx@spamto.devnul.com>
Subject: Re: Emacs Customization - newbie's question
Date: 01 Apr 2003 19:46:37 +1000 [thread overview]
Message-ID: <877kaeturm.fsf@tiger.rapttech.com.au> (raw)
In-Reply-To: mailman.3882.1049106807.21513.help-gnu-emacs@gnu.org
"Daniel R. Anderson" <dan@mathjunkies.com> writes:
> <snip>
> > > 1) Every book ever written about technology is outdated before it gets
> > > off the press
> >
> > True but this book is fairly outdated as it uses Emacs 19 which is two
> > major versions behind the curve.
> </snip>
>
> Have you seen the book? What is it that would go outdated? Are you
> trying to tell me C-x C-f doesn't open files anymore? Or that when I
> press C-v I don't just down the buffer a screen? Run over the
> changelogs. You´ll see that there is not a whole lot that has changed
> for the beginning user.
>
> Grab a book on C written 10 years ago and you won´t see radical syntax
> changes. Programs might be optimized for hardware which today can be
> gotten for free, but you could probably type in examples (so long as
> they use standard libraries) into a modern compiler and they would work.
>
Sorry, but I don't agree with this. Quite a lot has changed between
emacs 19 and emacs 21. Apart from user visible changes such as the way
font locking has evolved, there has been considerable change in the
internals of emacs which in turn leads to different ways of doing
things. Look at the number of packages which have/are being re-written
to utilize new features or ways of doing things.
While none of these seem too difficult to anyone who is familiar with
emacs, if you are learning and the book you are learning from is out
of date, your
1. likely to get very frustrated when things won't work the way
they are said to work in the book
2. learn bad habits or less optimal solutions which may have been
appropriate in the old version, but are not any longer.
Your analagy with C is IMO poor as well - C is a well defined
programming language which has had only minimal change over the last
30 years. Emacs is a whole working environment which has evolved
significantly over the last few versions - the move from 20 to 21 was
a major move and from memory one which was not achieved without some
hot debate because of the extensions and internal changes it involved.
Tim
--
Tim Cross
The e-mail address on this message is FALSE (obviously!). My real e-mail is
to a company in Australia called rapttech and my login is tcross - if you
really need to send mail, you should be able to work it out!
next prev parent reply other threads:[~2003-04-01 9:46 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-31 2:20 Emacs Customization - newbie's question Asene
2003-03-31 4:10 ` Daniel R. Anderson
2003-03-31 4:59 ` amh
2003-03-31 6:35 ` Daniel R. Anderson
2003-03-31 10:06 ` Adam
2003-03-31 10:32 ` Daniel R. Anderson
2003-03-31 18:32 ` Adam
2003-03-31 10:43 ` Daniel R. Anderson
[not found] ` <mailman.3885.1049107528.21513.help-gnu-emacs@gnu.org>
2003-03-31 11:43 ` Oliver Scholz
[not found] ` <mailman.3882.1049106807.21513.help-gnu-emacs@gnu.org>
2003-04-01 9:46 ` Tim X [this message]
[not found] ` <mailman.3878.1049092584.21513.help-gnu-emacs@gnu.org>
2003-03-31 16:27 ` Stefan Monnier
2003-03-31 6:43 ` Daniel R. Anderson
2003-03-31 22:39 ` kgold
2003-03-31 23:10 ` Stefan Monnier
2003-05-01 4:38 ` David Combs
2003-05-01 10:03 ` Roodwriter
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=877kaeturm.fsf@tiger.rapttech.com.au \
--to=timx@spamto.devnul.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.
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).