unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Rupert Swarbrick <rswarbrick@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: Re: Beginning Hobbyist Programmer Question
Date: Thu, 17 Jan 2008 16:47:57 -0600	[thread overview]
Message-ID: <vsednbO1lYOARhLanZ2dnUVZ8uCdnZ2d@giganews.com> (raw)
In-Reply-To: 44129c70-807a-4ef0-bc4f-e299caf5e334@k39g2000hsf.googlegroups.com

On Thu, 17 Jan 2008 14:04:46 -0800, signups17 wrote:
> Can anyone provide a cogent explanation for why I should take the time
> to climb that learning curve? What are the benefits, as you see them?
> 
> Also, assuming I'm convinced, can you point me in the direction of a
> good tutorial?
> 
> Thanks in advance.

Hi,

I'm not sure if there's an official FAQ for this group, but this sort of 
question comes up *a lot*. My comments:

1) emacs is fun to use (this _really_ is the most important bit in my 
opinion, and I've never encountered it in any other editor)
2) emacs is rather ludicrously customizable. You can write bits of elisp 
code to change pretty much any part of its behaviour. Although usually 
someone's done it in advance.
3) More generically, a powerful editor like emacs will allow you to avoid 
retyping/copying/pasting so much, since its replacing functions, macros 
and much more will allow you to rename the 70 variables you needed to add 
a dollar to in 5 seconds, without developing RSI.

Now, the previous bit was my personal opinion. About tutorials, 
presumably you mean an emacs tutorial (after all this is g.e.h), so:

1) Open up emacs and type C-h t (that is Ctrl-h followed by t) and read.
2) When you've finished reading that, there are numerous tutorials on the 
internet - you could always start at www.emacswiki.org

Other general comments I might make:

1) "why I should take the time to"... isn't a great way to get slightly 
hide-bound and clannish devotees of a text editor like me in a mood to be 
helpful.
2) In general, specific questions are much more likely to get good 
answers in a newsgroup. Looking quickly, I'd say that 9/10 of the first 
page of hits in a google search for "emacs tutorial" returns something 
useful. Maybe it would be worth trying that?


Rupert

  reply	other threads:[~2008-01-17 22:47 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-17 22:04 Beginning Hobbyist Programmer Question signups17
2008-01-17 22:47 ` Rupert Swarbrick [this message]
2008-01-18  0:26 ` reader
2008-01-18  1:44 ` Nick Roberts
2008-01-18  9:02 ` Andreas Röhler
2008-01-18  9:04 ` Thien-Thi Nguyen
2008-01-18 10:05 ` Stefan Kamphausen
2008-01-18 11:11 ` Daniel Pittman
2008-01-18 23:22 ` Alan Mackenzie
2008-01-19  0:19 ` Mike Treseler
2008-01-21 16:33   ` rustom
2008-01-22 17:24 ` Sebastian Tennant
2008-01-22 18:10   ` Mike Mattie
2008-01-23  6:02 ` Bob McCormick

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=vsednbO1lYOARhLanZ2dnUVZ8uCdnZ2d@giganews.com \
    --to=rswarbrick@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.
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).