From: "Joel J. Adamson" <adamsonj@email.unc.edu>
To: djc@resiak.org
Cc: help-gnu-emacs@gnu.org
Subject: Re: Failing to see the allure of Emacs
Date: Wed, 05 May 2010 13:27:35 -0400 [thread overview]
Message-ID: <5987.1273080455@chondestes.bio.unc.edu> (raw)
In-Reply-To: <9uudnY0F7J_qFjfWnZ2dnUVZ8oCdnZ2d@posted.visi>
[-- Attachment #1: Type: text/plain, Size: 3752 bytes --]
Sorry I'm coming into the game so late, I think my university has been
withholding mail from this list. I have a few points to add to the
discussion.
akaiser@visi.com <akaiser@visi.com> wrote:
> I can read source code and I do; but there's a lot of source code, and
> most of it is unrewarding reading. I can use info, but I don't like
> it. Please don't tell me "use info", because info is designed and
> intended not for reading, but for brief, casual online reference, and
> that is its cognitive organization.
Those ("brief, casual online reference") are called man pages. An info
manual is actually a printed book, laid out for reading *the whole
thing*. It is, in many ways, the opposite of a man page. Take any GNU
Manual and read it from the introduction and you'll notice that it
starts with concepts first. There are very clear standards about how to
write these manuals[1]. And whenever I take the time to read one from
the beginning it pays off hugely. Then when people say "How do you know
how to do that?" I say "I read the manual."
Also, if you really want to figure out how to work in Emacs, you can go
get a book about it[2].
If you don't "get" Emacs, that's fine. Go back to using Eclipse or
BBedit or whatever you like[3]. I think the reason people like me like
Emacs is because it is in line with their way of thinking. One that
includes always learning as much as you can.
Another thing to note is that when I first loaded Emacs (on Windows) I
didn't "get it" either. But after I read the tutorial and worked with
it a little bit, I knew that it was The Right Thing. Mainly because I
already had experience with Unix and remembered a time when I might have
used Emacs ten years previously (i.e. the commands were familiar).
Also, you don't have to do everything in Emacs. I just happen to use
mainly Emacs and Firefox, because my work consists mostly of coding,
email and looking things up on the web. I can accomplish most of that
just using Emacs. If your work is different, then that's your life and
no one should tell you to "just get it."[4]
My last comment is that you mentioned "going back to GUI." Are you
using a version of Emacs that doesn't have a GUI? If you are, you're
missing a HUGE advantage of Emacs. For one the menus have the
key bindings printed on the far right. For another, using Emacs with the
mouse is much more pleasurable and productive than using many other
(supposedly GUI-oriented) programs. You can do things with the mouse in
Emacs that you just can't do in other programs[5]. I noticed you're
using Windows, so try using Emacs on a Unix-like system and you'll
notice the difference. Copying and pasting with the mouse is way
easier; you can drag text from other applications and drop it into
Emacs; you can navigate tags and do lots of other things with Speedbar.
The only thing missing is dragging and dropping text in Emacs, but I
don't really miss it.
Emacs has an excellent GUI.
Joel
Footnotes:
[1] http://www.gnu.org/prep/standards/
[2] http://oreilly.com/catalog/9780596006488
[3] I won't make the suggestion that you go back to vi; I can't wish
that on another person without it weighing heavily on my conscience
[4] On the other hand, you'd be surprised how much work you actually
can get done this way ;)
[5] Show me the command for deleting a whole line with a single
double-click in Microsoft Word. Then show me how to go back three
occurrences of the word "word" in fewer than six keystrokes (without
typing the word itself). Word!
--
Joel J. Adamson
Servedio Lab
University of North Carolina at Chapel Hill
FSF Member #8164
http://www.unc.edu/~adamsonj
[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2010-05-05 17:27 UTC|newest]
Thread overview: 55+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-21 19:02 Failing to see the allure of Emacs Daniel
2010-03-21 20:22 ` David Kastrup
2010-03-21 20:47 ` Pascal J. Bourguignon
2010-03-21 21:00 ` akaiser
2010-03-21 21:26 ` Daniel
2010-03-21 22:16 ` Pascal J. Bourguignon
2010-03-22 4:05 ` Uday S Reddy
2010-03-21 22:21 ` David Kastrup
2010-03-23 17:22 ` akaiser
2010-03-23 17:52 ` Jeff Clough
2010-03-23 19:10 ` akaiser
2010-03-23 19:32 ` Uday S Reddy
2010-03-23 23:00 ` David Kastrup
2010-03-24 21:40 ` Tim X
2010-03-24 22:00 ` akaiser
2010-03-25 0:28 ` Jason Rumney
2010-03-25 1:03 ` Jay Belanger
2010-03-25 1:27 ` despen
2010-03-25 8:42 ` Tim X
2010-03-25 9:19 ` akaiser
2010-03-25 10:01 ` David Kastrup
2010-03-25 10:09 ` akaiser
2010-03-27 20:59 ` Giorgos Keramidas
2010-04-07 5:36 ` David Kastrup
2010-03-25 9:41 ` akaiser
2010-03-25 12:17 ` Tim Landscheidt
2010-03-25 12:24 ` akaiser
2010-05-04 19:03 ` Lennart Borgman
[not found] ` <mailman.28.1272999835.29092.help-gnu-emacs@gnu.org>
2010-05-05 7:15 ` David Kastrup
2010-05-05 20:40 ` Stefan Monnier
2010-03-25 12:45 ` Jay Belanger
2010-03-25 18:31 ` Uday S Reddy
2010-03-25 14:07 ` Ted Zlatanov
2010-03-25 14:49 ` David Kastrup
2010-03-26 4:14 ` Galen Boyer
2010-05-05 17:27 ` Joel J. Adamson [this message]
2010-03-21 21:02 ` Jeff Clough
2010-03-21 22:09 ` Pascal J. Bourguignon
2010-03-21 22:35 ` B. T. Raven
2010-03-21 22:45 ` Pascal J. Bourguignon
2010-03-22 0:21 ` Jeff Clough
2010-03-22 4:45 ` B. T. Raven
2010-05-22 2:38 ` Joseph Brenner
2010-03-21 22:58 ` John Bokma
2010-04-20 13:04 ` Jim Diamond
2010-04-20 17:15 ` Andreas Politz
2010-04-20 17:34 ` Jeff Clough
2010-04-21 14:26 ` Jim Diamond
2010-04-20 17:36 ` Glenn Morris
2010-04-21 14:31 ` Jim Diamond
2010-04-21 18:23 ` Stefan Monnier
2010-04-22 15:27 ` Uday S Reddy
2010-04-20 22:37 ` Tim X
2010-03-21 22:41 ` despen
2010-03-22 11:59 ` Stefan Kamphausen
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=5987.1273080455@chondestes.bio.unc.edu \
--to=adamsonj@email.unc.edu \
--cc=djc@resiak.org \
--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.