From: Stefan Kamphausen <skampi@gmx.net>
To: help-gnu-emacs@gnu.org
Subject: Re: Beginning Hobbyist Programmer Question
Date: Fri, 18 Jan 2008 11:05:30 +0100 [thread overview]
Message-ID: <85myr3a1p1.fsf@usenet.my.skamphausen.de> (raw)
In-Reply-To: 44129c70-807a-4ef0-bc4f-e299caf5e334@k39g2000hsf.googlegroups.com
signups17@gmail.com writes:
> 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?
Because in the end you will have /one/ tool to do almost all of your
typing ([1]) which will fit your needs /exactly/ ([2]). You will
never want to use something else. And of course: it's fun ([3]).
If I had no Emacs I were no programmer.
Regards,
Stefan
Footnotes:
[1] E.g.: Programming (C, C++, Perl, Python, Ruby, Java, Common
Lisp, Elisp, Bash, whatever), Writing (HTML, XML, LaTeX, groff,
plain text, emails, news, edit your oddmusewikis, whatever)
[2] Keybindings as you want them, code-templates, dabbrev,
spell-checker integration, your own extensions, things you found
on the 'net, integrated shell, integrated terminal, CVS and SVN
frontends, planning (org, planner, calendar, remember), etc.pp.
[3] E.g. writing elisp, finding astonishing features (like these
footnote-adding functions ;-)
--
Stefan Kamphausen --- http://www.skamphausen.de
a blessed +42 regexp of confusion (weapon in hand)
You hit. The format string crumbles and turns to dust.
next prev parent reply other threads:[~2008-01-18 10:05 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 [this message]
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=85myr3a1p1.fsf@usenet.my.skamphausen.de \
--to=skampi@gmx.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).