unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Daniel Pittman <daniel@rimspace.net>
To: help-gnu-emacs@gnu.org
Subject: Re: Beginning Hobbyist Programmer Question
Date: Fri, 18 Jan 2008 22:11:12 +1100	[thread overview]
Message-ID: <878x2ncrsf.fsf@rimspace.net> (raw)
In-Reply-To: 44129c70-807a-4ef0-bc4f-e299caf5e334@k39g2000hsf.googlegroups.com

signups17@gmail.com writes:

> Ok, I'm beginning to teach myself the art of computer programming. I'm
> starting with Python and I've built a few scripts that have increased
> my productivity tremendously at work, doing a lot of data crunching,
> etc.
>
> As I get more and more into programming, I get the sense that "real"
> programmers use emacs or vi, or some other editor that from my
> perspective, seems arcane and impenetrable compared to something
> simple like IDLE that comes with Python, or Scite, for example.

No, they don't.  A small proportion of them are very vocal about their
preferences, and only those two editors tend to excite enough noise and
support that you notice them.

Eclipse and Visual Studio are extremely popular systems for working with
Linux code[1], as are kate, the GNOME text editor, and a bunch of
others.

> Can anyone provide a cogent explanation for why I should take the time
> to climb that learning curve? 

VI?  Because it runs on every Unix in existence, and knowing a visual
editor that you can use in more or less the same way on any random Unix
system is a great skill to have.

Vim?  Because you want to run Emacs, but you like an editor with a mode
that goes beep and a mode that doesn't. ;)

(More seriously: Vim, because you want all the extra bells and whistles
 integrated into Vi rather than having to shift over to a shell to get
 at them.)

Emacs?  Because you want an IDE that is absolutely, totally custom to
your needs.  (or a mail reader that is, or ...)

> What are the benefits, as you see them?

For you?  None.  Learn to program with whatever tools you like.

Learn enough of Vi to edit files, even if slowly, because that is a
valuable skill -- but a completely different one from programming.


> Also, assuming I'm convinced, can you point me in the direction of a
> good tutorial?

For Vim, which is the stock Vi on many Linux distributions, try :help.

For Emacs you can start it up and hit C-h t (control and h, then t) to
get to the tutorial.  (or just read the front page.)

Regards,
        Daniel

Footnotes: 
[1]  Yes, /that/ Visual Studio, on that other platform.  I never
     understood why, but a whole bunch of people I know use it...

-- 
Daniel Pittman <daniel@cybersource.com.au>           Phone: 03 9428 6922
1/130-132 Stawell St, Richmond              Web: http://www.cyber.com.au
Cybersource: Australia's Leading Linux and Open Source Solutions Company

  parent reply	other threads:[~2008-01-18 11:11 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
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 [this message]
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=878x2ncrsf.fsf@rimspace.net \
    --to=daniel@rimspace.net \
    --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).